I would not take the risk of directly injecting data in the database of a proprietary software. The risks of messing up are big if you don't precisely know the organization and internal structures (relationships, etc...) of such a database.
I don't know how it works with QuickBooks, but usually vendors of such programs provide an ODBC driver (or another data interface library: ActiveX, etc...) that only allows to extract data from the database.
QuickBooks includes functionalities for importing data from an Excel worksheet. I would explore this path and use Automation in Access to create and fill such a worksheet, then import it into QuickBook. Otherwise, they probably have a help desk that should be able to help you.
qodbc can allow you to quickly and easily use SQL commands to add batches of data to your QuickBooks file with the use of commonly available tools like MS Access and .Net.
> I called QODBC and their answer was very confusing.
who did you speak to please? our product is a tool for programmers and advanced users and is not an end-user batch upload tool, so you would need to organize and program our tool to upload your data. There is also a tool called QIntegrator which supports batch upload, it comes with a level of import support that may help move you forward faster, whatever works for you.
> My question is, do I have to do anything else besides installing the driver and connecting my QB file with Access.
yes you would need to write a program to import the transactions to QuickBooks as they are entered or in batch mode.
> What I want is for data entry staff not to have access to quickbooks data and a simple form in which we can enter orders. I will also use Access to run reports and queries based on order data.
yes, it sounds more like you need a special form built in MS Access, our tool will let you or your IT staff build this with maximum speed.
> I would not take the risk of directly injecting data in the database of a proprietary software. The risks of messing up are big if you don't precisely know the organization and internal structures (relationships, etc...) of such a database.
sorry but this is not possible with QODBC as we are an ODBC driver which uses the QuickBooks SDK, and it does a pre-check on all transactions for integrity before allowing it to process against the database. It's not the fastest process in the world but it is guaranteed not to damage the database in any way because the SDK processes data in the same way as it does for manual entry.
Thank you very much for your responses. I have a transaction importer that i purchased in the past it is called "Transaction Pro Importer 3.0" and I also have the Exporter. Any idea if this would be compatible?