First, you shouldn't use Access/JET for a web site; use SQL-Server Express
instead if possible.
Second, you shouldn't use and ODBC provider instead of an OLEDB provider
with ADO unless you don't have the choice.
Even in the case of an OLEDB provider, when using Access on a web seerver,
you should put the ADO into single threaded mode (or apartment threaded
mode) instead of multithreaded (or free or both-threaded mode) by using the
makapt15.bat (or adoapt15.reg) file located on C:\Program Files\Common
but this will reduce the performance of all of your ADO applications. On
more recent versions of Windows, the makapt15.bat file has another name but
it's located at the same place.
Notice that even with all these precautions, you can still have some problem
if you have people directly accessing the backend Access database (using
Access as the frontend) at the same time as the web server.
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server