Welcome to the FAQ

Don’t forget to also check our forums if you don’t find an answer to your question here. This page is relatively new so expect it to grow rapidly. All our products support QuickBooks Pro, Premiere, and Enterprise 2004 – 2016.

OpenSync (23)

Although the QB documentation specifies that additional contacts for a customer will be returned in the ContactDetail table, this functionality is not currently implemented in QB. We create the ContactDetail table and have coded OpenSync and CoreObjX to handle it once Intuit remedies this issue. We are currently discussing this with them but have no indication when they will correct this.

The STATUS column is superfluous in child tables such as InvoiceLineDetail, SalesOrderLineDetail due to the one-many relationship between it and its parent record. If the STATUS column for the parent record is set, all child records will automatically be referenced and acted upon.

We only support .MDB files as they are a common denominator across all versions of Access. You can easily link an accdb format file to an MDB file from within Access. Segmenting your data and logic from the replicated QB data is our recommended practice anyway as it makes it much easier to upgrade the QB schema down the road to support newer versions of QB.

We’ve seen this error a few times and are working with the developers of our third-party license control to mitigate it but in the mean time the best solution we’ve seen is temporarily lower or disable User Access Control in Windows during the installation. Once the application is installed and all components registered, it’s perfectly fine to reset UAC to its previous level.

OpenSync supports multiple currencies and will extract all of the relevant information to the database. The only caveat is that when posting transactions it will not support override the default currency for the customer or vendor.

We’re looking to develop a simple document to illustrate these relationships – although many are very simple and repeated throughout – however since the database is modeled so closely to the QuickBooks XML specification you can use the Intuit documentation for further insight.

OpenSync works with all desktop versions of QuickBooks – Pro, Premiere, and Enterprise 2004 to 2017. It currently does not support QuickBooks Online or QuickBooks POS however we hope to include support for those platforms in the near future.

That is because OpenSync does not run as a Windows service. A decade of development against the QuickBooks desktop API has brought us – and many other developers – to the undeniable conclusion that the QuickBooks desktop API is simply not reliable when talking to it via a native Windows service environment. Consequently, we decided to roll our own service module – OSRunner.exe – you’ll find it listed in your Task Manager any time the OpenSync automated service is activated.

No. Not that we don’t want to but simply because up until now the demand hasn’t warranted the development cost. That said, if you’re interested in investing in the development, we’d be happy to speak with you.

The only way to obtain this information is to create a “Refresh Report” task that dumps the custom transaction detail report to a database table. Our schema is driven directly from the QB XML schema and the transaction query to QB does not return all of this information. That is why we disable it by default.

No. OpenSync does not support dumping multiple company files to a single database, you must have a separate database for each company file. The reason for this is that the internal ids used by QuickBooks (ListIDs and TxnIDs) are not guaranteed to be unique across company files.

The key advantage of OpenSync is the turnkey nature of it. You can install it and have QuickBooks data bi-directionally syncing within minutes. OpenSync is very much a desktop application which will permit anyone with even a modicum of technical expertise access to real-time QB data from the friendly, open confines of a relational database.

CoreObjX is a development tool. It is a COM-library – on which OpenSync was developed – that will require a programmer to implement. If you have the wherewithal, you can use CoreObjX to talk directly to QuickBooks without the need of a bridge database like what OpenSync would create for you. This is ideal for those who already have an application in place or for those who don’t necessarily need to export data out to a SQL database.

CoreObjX DB – an add on for CoreObjX – specifically accounts for 80% of OpenSync functionality by exposing extremely powerful create, refresh, and populate database methods which effectively emulate the comparable calls made through the OpenSync UI.

The only access to the audit trail information through the QuickBooks API is to retrieve the audit trail report. In OpenSync, you can create a task that will dump the audit trail report to a database table. Because of the API limitations there is no way to turn on/off the audit trail or delete entries.

To effectively move data to and from QuickBooks, there are myriad fields that need to be accounted for. Even if your database miraculously had all these fields present, it would still require you – through OpenSync – to complete an arduous and non-trivial process of mapping your data field to QuickBooks fields.

Our database is modeled directly against the full QuickBooks XML specification and therefore is set up, out of the box, to handle every transaction, entity, and list item the API makes available to us. We felt creating our own sync database was the most reliable and effective means of implementing a QuickBooks sync solution.

You would then write to and query from our database in order to read and write to your QuickBooks company file. For developers looking to integrate DIRECTLY with an existing database and would like to eliminate the OpenSync bridge solution, we recommend our CoreObjX library. It is a wrapper for the complex QB XML API and allows you to read and write directly to QuickBooks with as few lines of code as possible.

OpenSync is a 32 bit application and therefore requires the 32-bit MySQL ODBC connector. You can use any version greater than 5.1. If running on a 64-bit version of Windows we have had reports from users saying that they needed to uninstall the 64 bit connector before installing the 32 bit version.

Yes and no. If you run OpenSync with QuickBooks open, then no, it’ll simply utilize the license of whomever is logged in at that machine at the moment. If you run OpenSync unattended, then yes, it’ll require selecting the user account whom you wish to run OpenSync with.

While it will require initially being logged in as an ‘admin’ account to provide OpenSync permission to connect the company file, subsequent connections can leverage anyone under the caveat that OpenSync will only be able to access data that the user has been granted permissions to access. So if that user account has restrictions placed upon it, so will OpenSync.

This feature will be introduced in version 3.0. The reason is due to the manner in which version 2.0 was engineered and the degree by which it would be difficult to retrofit into the current architecture. That said, as long as you adhere to the intended data types, you can set them yourself without it impacting OpenSync operation.

AccessBooks RealTime (10)

We only support .MDB files as they are a common denominator across all versions of Access. You can easily link an accdb format file to an MDB file from within Access. Segmenting your data and logic from the replicated QB data is our recommended practice anyway as it makes it much easier to upgrade the QB schema down the road to support newer versions of QB.

We’ve seen this error a few times and are working with the developers of our third-party license control to mitigate it but in the mean time the best solution we’ve seen is temporarily lower or disable User Access Control in Windows during the installation. Once the application is installed and all components registered, it’s perfectly fine to reset UAC to its previous level.

No. OpenSync does not support dumping multiple company files to a single database, you must have a separate database for each company file. The reason for this is that the internal ids used by QuickBooks (ListIDs and TxnIDs) are not guaranteed to be unique across company files.

We’re looking to develop a simple document to illustrate these relationships – although many are very simple and repeated throughout – however since the database is modeled so closely to the QuickBooks XML specification you can use the Intuit documentation for further insight.

No. Not that we don’t want to but simply because up until now the demand hasn’t warranted the development cost. That said, if you’re interested in investing in the development, we’d be happy to speak with you.

This feature will be introduced in version 3.0. The reason is due to the manner in which version 2.0 was engineered and the degree by which it would be difficult to retrofit into the current architecture. That said, as long as you adhere to the intended data types, you can set them yourself without it impacting OpenSync operation.

CoreObjX (4)

Although the QB documentation specifies that additional contacts for a customer will be returned in the ContactDetail table, this functionality is not currently implemented in QB. We create the ContactDetail table and have coded OpenSync and CoreObjX to handle it once Intuit remedies this issue. We are currently discussing this with them but have no indication when they will correct this.

No. Not that we don’t want to but simply because up until now the demand hasn’t warranted the development cost. That said, if you’re interested in investing in the development, we’d be happy to speak with you.

The key advantage of OpenSync is the turnkey nature of it. You can install it and have QuickBooks data bi-directionally syncing within minutes. OpenSync is very much a desktop application which will permit anyone with even a modicum of technical expertise access to real-time QB data from the friendly, open confines of a relational database.

CoreObjX is a development tool. It is a COM-library – on which OpenSync was developed – that will require a programmer to implement. If you have the wherewithal, you can use CoreObjX to talk directly to QuickBooks without the need of a bridge database like what OpenSync would create for you. This is ideal for those who already have an application in place or for those who don’t necessarily need to export data out to a SQL database.

CoreObjX DB – an add on for CoreObjX – specifically accounts for 80% of OpenSync functionality by exposing extremely powerful create, refresh, and populate database methods which effectively emulate the comparable calls made through the OpenSync UI.

Consolidated Reporting (3)

The primary difference between our product and the built in functionality in QB Enterprise (QBE) is that you do not need to log into each company file as the report is being generated. Using QBE, this can become quite cumbersome as the number of company files grows. We also have the ability to customize the product if you have special requirements, of course this would involve an additional fee.

AccessBooks Updater (5)

The STATUS column is superfluous in child tables such as InvoiceLineDetail, SalesOrderLineDetail due to the one-many relationship between it and its parent record. If the STATUS column for the parent record is set, all child records will automatically be referenced and acted upon.

We only support .MDB files as they are a common denominator across all versions of Access. You can easily link an accdb format file to an MDB file from within Access. Segmenting your data and logic from the replicated QB data is our recommended practice anyway as it makes it much easier to upgrade the QB schema down the road to support newer versions of QB.

We’ve seen this error a few times and are working with the developers of our third-party license control to mitigate it but in the mean time the best solution we’ve seen is temporarily lower or disable User Access Control in Windows during the installation. Once the application is installed and all components registered, it’s perfectly fine to reset UAC to its previous level.

We’re looking to develop a simple document to illustrate these relationships – although many are very simple and repeated throughout – however since the database is modeled so closely to the QuickBooks XML specification you can use the Intuit documentation for further insight.