Why not attach your tables to the Access database using ODBC, then run
queries stored in Access ?

I've done this - devleopment using Access, then export the tables to SQL
Server and reattached to the Access database. Table adds are done to a
"loader" table in a local .MDB file, then moved over to the server using
e.g. "insert into tblOnServer select * from loadOnLocalDatabase" followed
by "delete from loadOnLocalDatabase" once the insert has succeeded.

Murff...

Greetings to Connectivity specialists out there.  I am looking for a
way to develop multiuser VB prototypes using ACCESS via ODBC.  This is
because our target DB environment will be ODBC compliant, and ACCESS
is desired due to its convenience and widespread usage.

I understand that the MSOFFICE ODBC driver for ACCESS (ODBCJT16.DLL)
itself does not work for VB3 as JET takes control and ignores ODBC.  I
am aware that through use of ODBC SDK I can force the use of ODBC, but
it defeats my purpose of having a easy to develop prototype.

Is there another way to get VB to pretend that ACCESS is another ODBC
compliant database, without VB resorting to use of its specialised JET
interface?

If there are no such alternatives, what is the next best desktop ODBC
DB (cheap, functional, easy to use) I should use?  How is SQLBase?
Personal Oracle?

Grateful for advice from experts in the field.