Ok, I built a database that is to be used by multiple people across the network. I built it so that it required minimal interaction with the backend.
Im now in the testing phase, and one of the checks I did was to see how it handled when two people accessed it simultaneously. Well it didn't work at all.
When my db opens, it first throws up the hourglass, then proceeds to relink to the backend tables. Once this is complete it proceeds to the login form.
So, if a user has the db already open, and somebody else trys to open it, the database hangs on the hourglass. Thus i'm assuming that it has something to do with relinking the tables.
Any ideas?
Im now in the testing phase, and one of the checks I did was to see how it handled when two people accessed it simultaneously. Well it didn't work at all.
When my db opens, it first throws up the hourglass, then proceeds to relink to the backend tables. Once this is complete it proceeds to the login form.
So, if a user has the db already open, and somebody else trys to open it, the database hangs on the hourglass. Thus i'm assuming that it has something to do with relinking the tables.
Any ideas?