I
Ihar
Hi
I have a split database (access 2007), with the front-end sitting on the
users local machine and the backend on a shared location on a Vista Business
x64 machine. The databases are saved in Access 2003 format, only because I
have one very stubborn user who refuses to upgrade to vista and office 2007.
Additionally I have a copy of the backend sitting on the users local drive
(laptops) for when they are out of the office. There is a form with a
button allowing them to choose which backend database they wish to use.
Now comes the problem.
In the office, when connecting to the shared backend, if they are the only
person connecting, response times are nice and quick. However, as soon as a
second person tries to connect, they (the second person) spend hours hanging
as soon as they press the login button on the main form, or if they have to
reconnect to the shared backend that takes hours and the person who was
working experiences seriously decreased response times. However, as soon as
the first person who was originally connected to the database disconnects
the second person who was hanging is able to work normally, with normal
response times.
Occasionally while hanging a message saying that the network connection was
interrupted will appear and then the procedure has to be restarted.
I have ensured that all tables are correctly linked and that both the from
end and backend databases are compacted, have tried getting users to logon
to the database in different sequences, but to no avail.
Any help that can be given on resolving this problem will be appreciated.
Regards
Steve
I have a split database (access 2007), with the front-end sitting on the
users local machine and the backend on a shared location on a Vista Business
x64 machine. The databases are saved in Access 2003 format, only because I
have one very stubborn user who refuses to upgrade to vista and office 2007.
Additionally I have a copy of the backend sitting on the users local drive
(laptops) for when they are out of the office. There is a form with a
button allowing them to choose which backend database they wish to use.
Now comes the problem.
In the office, when connecting to the shared backend, if they are the only
person connecting, response times are nice and quick. However, as soon as a
second person tries to connect, they (the second person) spend hours hanging
as soon as they press the login button on the main form, or if they have to
reconnect to the shared backend that takes hours and the person who was
working experiences seriously decreased response times. However, as soon as
the first person who was originally connected to the database disconnects
the second person who was hanging is able to work normally, with normal
response times.
Occasionally while hanging a message saying that the network connection was
interrupted will appear and then the procedure has to be restarted.
I have ensured that all tables are correctly linked and that both the from
end and backend databases are compacted, have tried getting users to logon
to the database in different sequences, but to no avail.
Any help that can be given on resolving this problem will be appreciated.
Regards
Steve