Quote Originally Posted by Tom.Net View Post
Any reason your not trying Sql over Access? Sql Server will give you all the connections ya need, plus as I said above connection pooling is extremly benificial to performance. It will (if coded so) allow each individual user to open as many connections as needed to perform a task. So if you have hundreds of records to insert by a single user, you can give them the permission to open as many connections as needed for the individual task.
And why should I need more than one connection (at-most two) at a time?? Isn't that an extremely bad design if I'm needing to do that anyways?