Strange lock issue

[quinton_bakies]

We have a 2003 DB that sits on a file server and is shared by multiple
users. Users on my LAN can all access the DB simultaneously without a
problem, but the user at a remote sight cannot open the DB if anyone is
in it. When the remote user tries to open the DB it just sits there
and does nothing, no error messages or anything. If no one is in the
DB then the remote user can open the DB without a problem. If the
remote user is in the DB my local LAN users can open the DB.

So basically the remote user has to get into the DB first and then my
local LAN users get in. Unfortunately this isn't practical because of
time zone differences and if the remote user exits the DB for some
reason my local LAN users all have to exit the DB for the remote user
to get back in.

It is a very strange problem. Can anyone help?

 

[Joseph Meehan]

We have a 2003 DB that sits on a file server and is shared by multiple
users. Users on my LAN can all access the DB simultaneously without a
problem, but the user at a remote sight cannot open the DB if anyone
is in it. When the remote user tries to open the DB it just sits
there and does nothing, no error messages or anything. If no one is
in the DB then the remote user can open the DB without a problem. If
the remote user is in the DB my local LAN users can open the DB.

So basically the remote user has to get into the DB first and then my
local LAN users get in. Unfortunately this isn't practical because of
time zone differences and if the remote user exits the DB for some
reason my local LAN users all have to exit the DB for the remote user
to get back in.

It is a very strange problem. Can anyone help?

Step one is to make sure that the remote user has full access to the
directory involved. That includes rights to create files, delete files and
edit files.

A quick test is to have that user create a new Word or other file, and
save it in that directory. Then edit the file and save it again and then
delete the file.

 

[aaron.kempf]

you're friggin crazy to use mdb in a real-world situation

use access data projects; ADP works a lot better than mdb performance
wise for multiple users

give it a chance; it's kinda hard to use

email me at (e-mail address removed) if you need help

-aaron

 

[quinton_bakies]

Unfortunately my company had a history of using Access for much more
than it was designed for. I'm the Network Admin and they have fired
our entire development team so I'm left holding the ball. I have
already told them that they need to move this to a SQL solution but
until then I have to keep things working.

I'm sure the permissions on the folder are the same for the remote user
but I'll check and post back.

 

[aaron.kempf]

moving to an ADP is quite easy

i just hate MDB; and it drives me crazy that people try to use it.

you know whose fault it is?

those goddamn MVPs are mdb-wimps; and they're scared to learn TSQL.

i'd reccomend finding someone to help you with this problem; email me
at (e-mail address removed) if you want me to make a reccomendation. i
know some really strong Access developers that can probably do this
remotely for you; it should be easy to diagnose. and it should be much
cheaper than you spending a week looking for an answer

-Aaron

 

[Joseph Meehan]

moving to an ADP is quite easy

i just hate MDB; and it drives me crazy that people try to use it.

you know whose fault it is?

those goddamn MVPs are mdb-wimps; and they're scared to learn TSQL.

i'd reccomend finding someone to help you with this problem; email me
at (e-mail address removed) if you want me to make a reccomendation. i
know some really strong Access developers that can probably do this
remotely for you; it should be easy to diagnose. and it should be
much cheaper than you spending a week looking for an answer

-Aaron

Are you on the payroll or something?

 

[aaron.kempf]

uh no im not.. i've worked for them in the past.

they're just the only folk i trust with access. everyone else treats
it like it's the ugly redheaded stepchild.

-aaron