I understand that ms access is quite limited in terms of the number of simulteneous hits it can process. If I create a seperate file for a table will the hits on that file interfere with hits on another file or by doing this would I be increacing the number of simulteneous users that can be serviced by my site?
i cant answer this for access, but i know that in mysql (where this isn't really a problem) if it *were* you can do table locking.
Basically, you call the table and say "lock it up for just me" and then all other requests are denied while the running script executes. After it's done, the next script can go.
However I'm not sure that the limitation is just in the number of simultaneous connections the Access files can handle. It might also be a limitation of the Jet database engine.
Interesting question. Someone should run some tests on it
Originally posted by akohl I understand that ms access is quite limited in terms of the number of simulteneous hits it can process. If I create a seperate file for a table will the hits on that file interfere with hits on another file or by doing this would I be increacing the number of simulteneous users that can be serviced by my site?
The magic number I read somewhere once was 255 simultaneous connections. Basically, if you're going to use MS-Access in a production environment, you need to drop your DB connections as soon as possible with either disconnected recordsets or dropping the recordset into an array.
Bookmarks