I'm starting a new project, and I need some input from people that have
successfully used MS Access 2.0 via ODBC from VB.

Why would anyone want to use ODBC to get to Access from VB?

Well, the reason is that we want to make  the application as generic as
possible so that later on it will be much easier to convert the system from a
VB/Access system to a VB/SQL Server system.

I would like input on tips/techniques  used to make the application as easy as
possible to modify later on if we decide to convert it to use SQL Server
instead of  Access.

Apparently it can not be done.  Somewhere in the support mechanism, I am
tempted to point at JET although I am not sure, there is an if statement that
returns an error if you try to connect to an access (*.mdb) database
via ODBC.  This at least is what happens if you use the bound controls, which
I am sure most would agree is the preferred way.

We had the same problem here and our solution was to postpone speculations
of platform independency for a while.

Of course there may be 3rd parties that sell data bound controls that do not
suffer from this, somewhat embarrassing, problem.

See also previous discussions in this group.

Magnus G.
EJS inc.