Access and ODBC

Nope. ODBC basically creates a DSN with the connection details. A request first locates the DSN and then uses it to locate the DB. There's server overhead associated with loading, accessing, and closing the DSN.

Using the DSN-less method (specifying the path to the db) recommended by WWF directly connects to the DB and avoids the extra overhead.

It's the Access Jet engine that handles the concurrent users, not ODBC.

MS Access is a very flakey DB to use in a shared environment. Performance and stability will be influenced by such things as the load created by too many sites on the shared server, the number of posts in the forum, the number of forums, the number of threads... etc. The number of users is just one factor but there's dozens of ways to max out an acccess db.

Turn off friendly http errors in your browser and post the actual error messages. Might help isolate what the problem is.

EDIT: - the followup error messages should be posted as a separate thead in the support forum for the WWF version you're using. You'll get more viewers there.


Edited by dpyers - 22 July 2006 at 1:32pm