Using coreObjX to integrate your application with QuickBooks helps you to deliver a more stable product in a shorter amount of time. Here's the logic:
If I_Write_Less_Code Then
I_Have_Less_To_Debug
If I_Have_Less_To_Debug Then
My_Product_Is_Ready_Sooner AND
It_Is_More_Reliable
End If
End If
It's that simple. With coreObjX you write less code to integrate with QuickBooks. When you write less code, you have less to debug and less chance of undiscovered problems. You deliver a more stable product in less time.
To demonstrate the difference, we built two applications to post an invoice to QuickBooks. One was built using coreObjX and the other using QBFC. The difference was dramatic. QBFC required 185 lines of code to coreObjX's 43 lines of code. That's over a 4 to 1 savings in lines of code! And that's a very simple example! When you start adding functionality coreObjX saves you more, even up to 10 times fewer lines of code!
But that's not the full story. coreObjX code is easier to write. That's because coreObjX implements true business objects for all of the entities in QuickBooks. You interact with Customer and Invoice objects, not objects that model an XML API. With full code completion and support for all built-in QuickBooks enumerations, you'll almost never need to consult our thorough context sensitive help. The result? Less time for each line of code.
coreObjX is implemented as an ActiveX DLL exposing all QuickBooks objects as standard COM objects. That means it can be used from any language that supports COM components including Visual Basic, C++, FoxPro, Delphi, Powerbuilder and many others.
Please check our FAQ for any questions you may have regarding CoreObjX.
Supported QuickBooks Versions
Other Requirements