The QODBC Remote Connector and the iBiz Remote Connector are only mean't to be used with desktop applications. For example, that Excell user that doesn't have QuickBooks on their workstation. When it comes to anything that runs as, or through, a Windows Service, the QODBC Server Edition and QODBC DCOMs must be used and run against QuickBooks on the server itself. The company (.qbw) file can be on another server via a network or even VPN mapped drive if need be. 

Most users tend to use queries like:

SELECT * from Customer

which will run slowly as QODBC has to display the correct current balance for each customer, while this will run much faster:

SELECT "Name","LastName","FirstName","BillAddressAddr1",
"BillAddressAddr2","BillAddressCity",
"BillAddressState","BillAddressPostalcode"
from Customer

However you can also override your QODBC Optimizer configuration screen settings to suit what you are actually doing by using the following tags:

VERIFIED | VERIFY - Forces Full Resync with QuickBooks on the optimized table before Query starts
CALLDIRECT | UNOPTIMIZED - Passthru query directly to QuickBooks - use no optimizations
OPTIMIZE | OPTIMIZED | NOSYNC - Passthru query to optimized table directly for maximum speed

Examples:

select * from InvoiceLine UNOPTIMIZED
select * from InvoiceLine NOSYNC
select * from InvoiceLine VERIFIED

For example, to read new (recent) InvoiceLines directly out of QuickBooks use:

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

Or you can resync your optimized InvoiceLine table by first doing:

sp_optimizefullsync InvoiceLine

then read directly out of the optimized table by doing:

select * from InvoiceLine NOSYNC WHERE Txndate > {d '2008-01-31'}

This is very f...a.......s.................t.

Another good example of using NOSYNC would be to get for example all historical invoicelines before 2003:

SELECT * from InvoiceLine NOSYNC WHERE Txndate < {d '2004-01-01'}

as invocies before 2004 don't ever change, you can read them directly from the QODBC Optimizer. You just need to use unoptimized for crtical operations like Sales Commisions etc.

As far as running QODBC with a web browser is concerned, see: How can I see QuickBooks data in a Internet Explorer Browser using Windows XP?  for the setup info behind using QODBC via IIS. Most issues have to do with security setup. What type of security have you setup on the server? There can be all sort of permissions issues with IIS using AUTHENTICATED USERS. Sometimes the *shotgun* approach of giving everything that has the words QODBC in it is the only way....

See the last post in: Permissions Issue with IIS using AUTHENTICATED USERS