I've reviewed your documentation on creating a linked server to SQL Server, but the screen shots and descriptions seem to reference Microsoft SQL Server 2000, not Microsoft SQL Server 2005.  Following the instructions for 2000, I was able to extrapolate what I needed to do, for the most part, but the "provider options" were not the same in SQL 2005, so some of those options could not be set as described in this post...

http://www.qdeveloper.com.au/forum.php?homeinclude=topicdetails&forum_id=1&category_id=2&post_id=205

I am able to create a linked server, but I'm not getting any test results back, when I know I should be.  I can create a linked table to Access to view the data, but the linked server doesn't allow read access (I haven't tried the insert/updating yet.)

Here is what I'm seeing when I create the linked server in SQL Server 2005 by using the instructions for SQL 2000....

Beyond that, it appears that it pegs out the cycles on the processor (as if it's creating multiple QODBC catalogs.) 

Also, since QuickBooks Application apparently needs to run on the server in order to get any type of results back, I'm thinking that the server solution just won't cut it.  I don't think this is so much an issue of the ODBC driver as it is of the file-based architecture that QuickBooks uses.  It just doesn't seem ready for prime-time use. 

Please tell me were I'm going wrong here.

Thanks!