Access/Citrix

[Karen]

I have a database built in Access that is on our Windows Server. We
have a satellite office in Houston that uses Citrix to access our
server. Here in the main office, we have 15 users that log directly
into the LAN; there are 4 users that dial in via Citrix.

We have constant errors in our Home office that someone has locked up
the database and entry is denied. When this happens (at least 5 times
a day), I have to contact the Houston office and ask everyone to save
their work and exit the system, thereby releasing it for opening in
our office. At that point, New Orleans and Houston can log in and
work simultaneously.

I don't understand why Houston has the ability to "lock" out the users
in New Orleans. I don't have a clue as to where to start to
troubleshoot this problem.

Is there a setting that allows users to open the program exclusively?
If so, is this a setting in Access itself or is it in the database?
Is there a way to force the users (or access) to close after so much
time has elapsed with no activity? Is there a way for me to cut the
connection from here?

Have I completely missed the issue? Please help.

Thanks.

Karen

[paii]

Look for comments in your messages.

"Karen" <kr****@portlite.com> wrote in message
news:50**************************@posting.google.c om...

I have a database built in Access that is on our Windows Server. We
have a satellite office in Houston that uses Citrix to access our
server. Here in the main office, we have 15 users that log directly
into the LAN; there are 4 users that dial in via Citrix.

We have constant errors in our Home office that someone has locked up
the database and entry is denied. When this happens (at least 5 times
a day), I have to contact the Houston office and ask everyone to save
their work and exit the system, thereby releasing it for opening in
our office. At that point, New Orleans and Houston can log in and
work simultaneously.

I don't understand why Houston has the ability to "lock" out the users
in New Orleans. I don't have a clue as to where to start to
troubleshoot this problem.

Is someone in Houston opening you backend database?
Does each Terminal server user have a private copy of the frontend?

Is there a setting that allows users to open the program exclusively?
Access on the Terminal server may be configured to open exclusive. Open
exclusive will not be a problem if everyone has a copy of the front nd. It
will be a problem if the backend is opened.

If so, is this a setting in Access itself or is it in the database?
The setting is in Access.
Is there a way to force the users (or access) to close after so much
time has elapsed with no activity? Is there a way for me to cut the
connection from here?

You could use the OnTimer event on a always open form.
You could program you application to look for a shut-down message on the
backend.
Have I completely missed the issue? Please help.

Thanks.

Karen

[mgoodrum]

Karen,

How long can Houston and New Orleans work before the lockup? Are the
users writing data to the database or are they read-only? Which
version of MS Access? Has the lockup ever occurred when Houston was
not logged in?

My initial guess is that if Houston, and New Orleans can work for any
period of time, then the lockup occurs. The database is not being
opened exclusively and that some other event is causing the lockup.
Data collision, or some code that MS Access trips over, due to the
delay in the Citrix.

Have you looked inside the .ldb file to see which users are in the
system, when the database is locked up?

Feel free to email me directly at mg******@aol.com if you have any
additional questions.

Thanks
Mark
kr****@portlite.com (Karen) wrote in message news:<50**************************@posting.google. com>...

I have a database built in Access that is on our Windows Server. We
have a satellite office in Houston that uses Citrix to access our
server. Here in the main office, we have 15 users that log directly
into the LAN; there are 4 users that dial in via Citrix.

We have constant errors in our Home office that someone has locked up
the database and entry is denied. When this happens (at least 5 times
a day), I have to contact the Houston office and ask everyone to save
their work and exit the system, thereby releasing it for opening in
our office. At that point, New Orleans and Houston can log in and
work simultaneously.

I don't understand why Houston has the ability to "lock" out the users
in New Orleans. I don't have a clue as to where to start to
troubleshoot this problem.

Is there a setting that allows users to open the program exclusively?
If so, is this a setting in Access itself or is it in the database?
Is there a way to force the users (or access) to close after so much
time has elapsed with no activity? Is there a way for me to cut the
connection from here?

Have I completely missed the issue? Please help.

Thanks.

Karen

[Pete]

kr****@portlite.com (Karen) wrote in message news:<50**************************@posting.google. com>...

We have constant errors in our Home office that someone has locked up
the database and entry is denied. When this happens (at least 5 times
a day), I have to contact the Houston office and ask everyone to save
their work and exit the system, thereby releasing it for opening in
our office. At that point, New Orleans and Houston can log in and
work simultaneously. Is there a setting that allows users to open the program exclusively?
If so, is this a setting in Access itself or is it in the database?
Is there a way to force the users (or access) to close after so much
time has elapsed with no activity? Is there a way for me to cut the
connection from here?

Have I completely missed the issue? Please help.

Thanks.

Karen

I've had my own share of problems with Access 97 and Citrix/Terminal
Server. The one thing you haven't mentioned is if you have disabled
opportunistic file locking on the file server and the Citrix client
machine. I believe that *disabling* oplocks will solve your problems.
If you want to read up on an eerily similar situation, check my
thread for some of the fixes:

http://groups.google.com/groups?thre...ases.ms-access

Pete