I am still in the evaluation version of QODBC, V7, and using Quickbooks Online.

We can see the Customer Table has data, but invoices, sales receipts both have NO data, they open with no entries.  If I run Quickbooks Online, I see my receipts and my invoices, so I know there are invoices and receipts.

Any suggestions?

Thanks.

When over 1000 records could be returned by any given query to the QuickBooks Online Edition, the query get's terminated by QBOE at the Intuit end. Assuming that you have entered invoices since January this year, you need to query a smaller subset of records like this:

select * from InvoiceLine UNOPTIMIZED WHERE Txndate > {d '2007-01-01'}

Where the date format is {d 'YYYY-MM-DD'}

You can also remove the UNOPTIMIZED tag if it works as I've only added it to bypass your local optimized invoice and invoiceline tables in case there's something wrong there. You should always use the QODBC Optimizer with using QBOE.

OK, using the code you show, I am able to see some records.  However in the 4 queries I ran, Access crashed 3 times.  It's the "we're sorry, Access has encountered and error and needs to close" type error, where it proceeds to make a backup then re-open.  This is a clean database with just the OQDBC links and now 3 pass-through queries.  There's no code yet, no other tables, nothing else. 

I am wondering if QODBC is really this unstable, or if the instability is due to Quickbooks Online, or what.  I really wonder if it's worth continuing to develop with this if the Access database is going to crash this often (75% of the time).

I even simplifed the query to select just one invoice that I already know is in the database.  That's not going to be useful long term, but I am trying to figure out how to use QODBC within Microsoft Access, and keep Access happy.  I don't quite understand why this is so difficult.

I suggest you use VB Demo to test your queries first. Incorrect syntax can crash MS Access. Please ensure that you are using QODBC v7.00.00.214 (or higher) as earlier versions (like Build 207) did crash MS Access at times.

See: How can I get the latest version of QODBC? 

I'm using VB Demo (although I don't understand why this is any better than Access - the demo doesn't tell me if the query is correctly written or not).  The query you suggested works, but only with the UNOPTIMIZED keyword.  In other words this query returns records:

select * from InvoiceLine UNOPTIMIZED WHERE Txndate > {d '2007-01-01'}

and this query returns no records:

select * from InvoiceLine WHERE Txndate > {d '2007-01-01'}

Why?  I have optimizer checked on in the configuration.

Ok, please switch off (uncheck) the QODBC Optimzer and then the product will run as expected without the need of using the UNOPTIMIZED tag.