Problems with multiple users?

[Guest]

At our business we have an software application based on ms acces. But we
have some troubles and ask our selves if it is the software, acces or our
network.

If we have multiple users using the system at the same time, some
workstations won't open the software we get an error saying couldn't find the
file. But that only on a few workstations.

If no one is using the system execpt the bad workingstation, there is no
problem, but as soon as an other workstation logs onto the system. The bad
workstation gets cut of, does anyone no if it is an acces problem our do we
need to look at our network ?

 

[Lynn Trapp]

Do all the users have read, write, and delete permissions to the folder
where the Access database resides?

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html

 

[Guest]

Yes they have, we tested if there were any trouble with mapping our network
settings. But if we made a simple one form acces file we encoutered the same
problems.

thnx for the response

 

[Larry Daugherty]

You may have a flaky NIC on the "bad" machine. Given that the "NIC"
is usually on the motherboard it could be impossible to troubleshoot.
You might try swapping another machine, that presently works well, in
its place and see if the problem persists. If the problem is still
local to that node on the network then it's specific to that node of
the network. If the problem is corrected by running the other machine
with similar loading of the BackEnd, then the problem is in "bad".

HTH

 

[SusanV]

Or, if you can't or don't want to change out the machine, you can disable
the onboard NIC via the BIOS and add a PCI NIC to test this.

Susan

 

[Albert D.Kallal]

Do remember that users need full rights to that directory. Those rights
include create, and deletion rights.

Ms-access creates a temp "ldb" locking file. If that file cannot be created,
then the database opens in exclusive (non multi-user) mode.

So, depending on who gets in first can effect the behavior (if the first
person in can create the locking files, then it is multi-user, but if the
first person in can't create the locking file, then you single user).

So, when we say you need full rights to the shared folder on your server, we
do mean full rights.

I also assume that the software is installed on each computer...right?

 

[Guest]

The ldb file is created I checked that allready, the software is installed on
each system and the database is on the server. The user rights are properly
set, the problem has shifted to all systems, we encouter the problem that
there is one computer that gains all the "software speed" and rights when it
opens the system.

It isn't just an local problem (so one bad system) it now became a problem
on each system.

This is a mind breaking problem, all the employees are breathing down my
back because the software won't opperate properly when multiple users use it.

 

[Albert D.Kallal]

The ldb file is created I checked that allready, the software is installed
on
each system and the database is on the server. The user rights are
properly
set, the problem has shifted to all systems, we encouter the problem that
there is one computer that gains all the "software speed" and rights when
it
opens the system.

Are you now saying that things work, but very slow?

If yes, then you need to keep a persistent connection open from the front
end to the back end....

For issues of performance, you want to check out the following list:

http://www.granite.ab.ca/access/performancefaq.htm

The above mentioned the persistent trick that 9 out 10 times restores the
performance.

 

[dallas]

ok

The ldb file is created I checked that allready, the software is installed
on
each system and the database is on the server. The user rights are
properly
set, the problem has shifted to all systems, we encouter the problem that
there is one computer that gains all the "software speed" and rights when
it
opens the system.

It isn't just an local problem (so one bad system) it now became a problem
on each system.

This is a mind breaking problem, all the employees are breathing down my
back because the software won't opperate properly when multiple users use
it.

 

[Guest]

Hi Albert,



I followed your instruction in this link
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm but when I
finished the FE on another computer, we cannot add data on the database at
the same time.



It will say that the record set is not updatable. But I already removed the
locks and the DB should be shared.



To give you a brief history on the database, I made a BE and placed in the
shared folder. A copy of the FE is in the same folder which is an mde file. I
have the original in my own workstation. I left a copy of the FE so the other
workers can copy and paste it in their own workstation.



But when they open their copy of the FE in their desktop, they cannot add
any data to the database.



Do you have any suggestions for me what to do?



Thank you so much.

 

[Guest]

Yes Bob, the DB is placed in a shared folder and everybody have permission to
write and edit anything in that folder.