No you can not use an ODBC connection over the net to a jet backend mdb
database file. The reason for this is jet is not a socket based system like
the SQL server, and therefore you can't connect over a tc/ip connecton
*unless* you use windows networking. If you look closely at any odbc
connection strings, they **always** resolve to an absolute full file path
location sitting on a computer.

That means the software accessing data from that file must be able to
physically see the file sitting like a regular windows file in a computer
directory. You can no more use ODBC to connect to word, PowerPoint either.
In other words you must be able to physically open the file like any other
power powert file, a word document, or a plain Jane windows file. There's no
database server when using JET, but just the fact that you are opening a
file. You are simply using the windows file system to open the file.

An ADP will not work in this case unless you are using SQL server (adp ONLY
works with sql server). On the other hand, if you're using SQL server, then
you can connect you mdb front end now via odbc. unless I completely misread
your question, you said that you're not using SQL server at all here, and
are only going to be using jet. (is absolute critical that you have this
issue clarified here).

MS access in fact does not use ODBC to connect to the back end (unless
you're talking about linked tables to SQL server). Note that you can write
code on your local machine that uses a odbc driver, but you're **still**
physically using the windows file system to open and access that jet file in
all cases. Jet does not run as a separate thread or process from your code
that you useing to develop your software with. It becomes part of the actual
code library that you're using.

Your only choice is to manage this file are:

1)
You use DDL commands (drop table, create table, alter table etc.). You thus
simply send commands via whatever programming language you use. There is a
DDL the language reference in the help, at least there is for access 2003
(however, keep in mind that you're not really using MS access anymore,
you're using what's called the jet engine -- it is simple to realize this
issue because in fact you're not installing MS access on the web server, are
you?). Anyway,  virtually any of the processes of creating tables, deleting
tables, and adding fields can be done via SQL ddl commands. that's how you
manage the database.

2)
Simply FTP a copy of the mdb file down to local computer, make the
modifications, and then upload (ftp) it back your web server.

Note that before you grab a copy of this mdb file, you'll have to go into
your website management system, and stop the web server, or at least force
it to close the mdb file because it could be likely that the web server has
that file opened and in use at that point in time. Just like on your regular
computer, you can't really make a copy of mdb file while it is open and use
by other people (in this case likely the web server has the file open). To
be honest I have on many occasions copied the file while it is in use by
others. However what you most certainly can NOT do is copy the mdb filed
back up to the server and overwrite the existing mdb file while it is use by
others. At the very least I suspect you have to delete the mdb file on the
server first if you're not given management tools to stop or de-attach the
web server from that mdb file that is open.