Client/Server Application issue

[Jeff]

Hello,

I have designed many Access Client Server Applications before where I have
the 1 MDB file on the Hard Drive & the data MDB file on the server & have the
Tables Linked.

For this one client when I do the same when 1 user logs in they are fine.
But when anyone else does they freeze & they have to End Task out of Access.
So basically it is only allowing 1 user to log in. So that is my problem &
that is what I am looking for a solution for. Should be able to have 3 or 4
users on at the same time. The weird thing too is if 1 user is logged in &
then when another tries & they freeze, if the original user logs out, then
they will unfreeze & can go in.

Thes are some of things I tried/looked into:
- They have a good server, 3ghz 1GB RAM
- IT person made sure users had full rights to folders
- I tried compacting & repairing
- I tried brand new Access files & copied over all objects.
- It is a small database, hardly any data in it.
- They have Access 2000, Service Pack 3

I am stummped. Does anyone have any advice ?

Any help would be greatly appreciated.

Thank you,
Jeff

 

[Jeff Boyce]

Jeff

When my multi-user application suddenly started shutting out all but the
first person in, I spent three days trying to track down why.

The bottom line was that some (network) person had altered permissions at
the share, or folder, or file level, ... and hadn't bothered to inform
anyone.

The first place I'd (re-)check is permissions.

Also, is there any chance the application is being opened for exclusive use?

Regards

Jeff Boyce
<Office/Access MVP>

 

[Jeff]

Hi Jeff (cool name),

Thank you for responding.

I also have been pulling my hair out of my head.

- I double checked, the Cleint file & the Database file are set to Open in
Shared Mode
- As far as the permissions, I was working with an Network Admin here &
according to him all rights have been assigned to the Shared folder. We even
tried logging in as Admin & still same problem.

Here is something else I just tried & noticed:

I have the 1 user logged in & so it would freeze for another. On that
second machine I open up the program in Design mode & go to the VB Editor &
Step through the code as this one opens. Every time I have a line of code
that references the database, ex. Dlookup, DCount it takes about 4-5 seconds
to execute that 1 line of code. But it does work & gets the value. Then if
I step through the rest of the code the program opens up. So it has
something to do with the timing.
If I let it go it freezes, if I step through line by line slowly it opens up.

Any other ideas ?

Thank you,
Jeff

 

[Jeff Boyce]

Jeff (yes, the name rocks!)

The other major slow-down issue I've had to deal with came after our agency
received a "transparent" update to our antivirus checking software. It
seems it took exception to the way Access talks back/forth between the
front-ends and the back-end.

Don't know if it will help, but best of luck on your detective work!

Regards

Jeff Boyce
<Office/Access MVP>