While testing an Access 2000 application this week we noticed a strange anomoly.
The environment:
Multi-user,
Windows XP clients on which the "program" data base container reside,
The "tables" data base container resides on Server 2003, tables are linked to the individual "program" data base container on each user's PC.
Forms specify "Lock editted record" & "Dynaset (Inconsistant Update)".
The problem:
While testing the program we used .MDB containers on two clients. The response time while opening the same form to the same record was okay (<= 2 secs) for each user. When we generated an .MDE from the .MDB the response time on the second user opening the form to the same record was extremely slow (approx. 1.5 mins). If the first user closed the form, the form opened immediately on the second user. Our first guess was that the locking was prohibiting the second user access to the form/record. After a bit of testing, this did not prove to be the case, since in every instance the first and second user's response time was approximately equal using the .MDB & the second user was locked out of updating the data (which is what we want). However, in each test case the second user was slower than the first using the .MDE.
Did we miss a parameter or is there a coding technique around this?
Thanks for any help.
The environment:
Multi-user,
Windows XP clients on which the "program" data base container reside,
The "tables" data base container resides on Server 2003, tables are linked to the individual "program" data base container on each user's PC.
Forms specify "Lock editted record" & "Dynaset (Inconsistant Update)".
The problem:
While testing the program we used .MDB containers on two clients. The response time while opening the same form to the same record was okay (<= 2 secs) for each user. When we generated an .MDE from the .MDB the response time on the second user opening the form to the same record was extremely slow (approx. 1.5 mins). If the first user closed the form, the form opened immediately on the second user. Our first guess was that the locking was prohibiting the second user access to the form/record. After a bit of testing, this did not prove to be the case, since in every instance the first and second user's response time was approximately equal using the .MDB & the second user was locked out of updating the data (which is what we want). However, in each test case the second user was slower than the first using the .MDE.
Did we miss a parameter or is there a coding technique around this?
Thanks for any help.
