We were using Enterprise 2017 for a couple of years – with Opensync 2.0
with no problems at all.
We upgraded from enterprise 2017 to 2019
Upgraded Opensync from 2.0 to 3.0
We are getting all sorts of errors from our Database SQL stored procedures
“Error Converting data type varchar to numeric”
“Item cannot be found in the collection corresponding to the requested name or ordinal”
Qtn #1 Are there any major database design changes in Qbooks 2019
Qtn #2 Are there any changes in Opensync 3.0 ?
What are we missing that its no longer working?
OpenSync v3 database has its fields properly typed. You will have to create a new database with OpenSync v3 and run a full populate. Depending on hoe far ago our database is, it could be new fields and even new tables added to it. We also change the location of configuration folder because the new windows restrictions. New the configuration will be by user. You create the configuration file on one user and import it on the other in case you have a multi-user environment.
Thanks Yudel for the update.
Yes because the field format types have changed and new columns added – it has thrown all the coding (stored procedures ) we built around open sync 2.0 off.
Wheer acn we find more info on field types and the database structure changes/
Is there a pdf or link?
We need to recode everything based on the database architecture
We don’t have the documentation that detailed as you are asking me. But if you create an access or SQL Server database, you will be able to see the field type and any column that could be added to it. Sorry for the inconveniences.
You must be logged in to reply to this topic.