-Borg- Don't know what context the statement was made it, but they may be talking about connections through an Access/Jet application on a LAN, which, I believe, are less than 255.
Term "connections" is misleading. I't doesn't mean what zaboss thinks it does. A concurrent connection can be thought of as a specific low-level data base activity - e.g. a read, a write - not as the connection you open in your script to a db.
MSDE (SQL200 Desktop) for example supports 5 concurrent connections. Which means it can support a couple of hundred users. Because of the way MS SQL2000 handles it's low-level activity compared to Access's Jet DB Engine, you can support more users with MSDE's 5 connections than with Jet's 64/255.
Topic Options
Post Options
Thanks(0)
The Microsoft drivers provided currenly for Access only allow 64 concurrent
connections on a per-server basis, as such, you can experience timeout problems
in your script if you are on a shared server with other customers who use Access
heavily also, as the server will be sharing the 64 connections as a whole.
