If you are considering a QuickBooks custom report project for your company you need to be aware that there are some limitations on direct data access, due to restrictions and/or intentional omissions on Intuit's part, that can impact both development times and costs as well as report run times.

Run-time issues are generally more pronounced when developing QODBC based reports and this is one of the reasons that we recommend development of custom QuickBooks reports be done using Synegration's AccessBooks Realtime as your data access layer. This holds true regardless of whether you plan to do the development yourself or hire a third party to do your development.

Here at 4Sight we can work around these limitations and, in most cases, we can still build reports based on data that the QuickBooks SDK does not provide direct access to. To do this it is necessary to pull the data by running QuickBooks built in reports, capturing the data returned to a table and linking that returned data to the other native QuickBooks tables that underlay the report being built. This process which can add considerable run-time overhead to a report when developed using QODBC as the data access layer.