Help! Users can't access database in a domain...

[Devon the Consultant]

Hi all -

We're supporting a client who has a hashed up Access system which uses
a central MDB store which is connected to by Access clients (I presume
via linked tables/record sets, etc...)

We've upgraded their server which was improperly configured and have
now set up the database in a domain.

Having created a similiar system myself - we've ensured that the path
is identical to the old server through the drive mapping - and with
administrative rights, the users are able to access the database fine
using their Acess client (although some complain of slow performance at
times)

This issue is when we demote the users to a normal user account in the
domain - suddenly the clients cannot connect at all.

Having read through some of the threads - we have ensured that the
users have all permissions to the directory and the MDB file with the
exception of 'full control' - but still no joy.

Can anyone suggest what the issue is?
As a test, I asked my supervisor to open the MDB file directly from one
of the user machines and he is getting a 'read only' message on
load-up.

This message does not appear when the file is opened from a client
machine with an administrator account.

 

[Arvin Meyer [MVP]]

Users need everything but full control on the directory on the server AND on
the directory of the front-end on their own workstations.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access

 

[Devon the Consultant]

Hi Arvin - I just discovered this myself no less than 5 min ago -
thanks for your reply!

Do you have any suggestions about the performance issue?

cheers...
Devon

 

[Devon the Consultant]

Hi Arvin - I just discovered this myself no less than 5 min ago -
thanks for your reply!

Do you have any suggestions about the performance issue?

cheers...
Devon

 

[Larry Linson]

Do you have any suggestions about the performance issue?

The sites of two MVPs have excellent information and links on performance in
and avoiding database corruption in multiuser environments. MVP Tony Toews'
site, http://www.granite.ab.ca/accsmstr.htm, and MVP Jeff Conrad's site
http://home.bendbroadband.com/conradsystems/accessjunkie.html. Take a look
and post back here if more questions.

Just my NSHO, NT 4.0 and Win 98 SE seemed to be the "golden days of Access
multiuser performance" -- not because the OSes were better, but because the
default settings were just right for Access multiuser, so even the
not-so-knowledgeable had great success. Now, it may take a little more
tweaking, but good performance and avoiding corruption is still possible,
and the OSes are better, too.

Larry Linson
Microsoft Access MVP

 

[Devon the Consultant]

I will check out the links - thank you.

The performance issue does seem a bit strange. At times, the database
runs very smoothly but can slow down and even halt entirely for users.
In further examination, I observed that the slowdown is not consistant
with the number of users online nor the functions being executed.

The only strange thing is that users commented the issues seem to be
worse in the afternoon. As their usage is no different in the
afternoon than in the morning - I am having a hard time locking down
the problem. I have confirmed that there are no server maintenance
operations in progress during this time (they are set to occur at 2am).

The only thing I can think of is something getting in the way such as a
virus scanner or firewall.

 

[Ron2006]

The real question to ask is not how hard are your users using the
system in the afternoon, but how hard is the server being hit in the
afternoon. That may take some hardware/software watching the server
use.

things like error rates going up because some junction box is in the
sun in the afternoon and it is getting overheated
or the cable goes right by the AC motor in the afternoon.

But it is something that the network gurus may have to sniff out. The
trick is getting them to believe you.

 

[Devon the Consultant]

Sounds a bit far fetched, but I'll check it out.
Thanks.

 

[Ron2006]

All I am really trying to say is that it may have nothing to do with
what your people are doing.

And it can be farfetched at times. My instructor for a networking
class, had problems with their wireless network recently and they
finally figured out that a business neighbor had changed the place he
was parking his truck. His new parking place was just enough in the way
of their wireless network antenae that it caused a problem. They
figured out another place to park the vehicle and those problems in the
afternoon went away. They have since moved the antenae also, But the
problems can be caused by many things, is all I am really trying to get
across.