Is Access a multi-user application

[Guest]

I've been using access for 8 plus years and have never had problems with multiple people accessing the system (except if rights were not set up to accommodate sharing on the server)

As long as the .ldb file was created in the same directory as the .mdb file everything works great. In the past three weeks though I have had multiple databases that are only allowing one user per time to access the system even though the .ldb file resides in the directory. We now are getting errors that say "mysysadmin" already opened exclusively....

In talking to our network people I received the following messge

Regarding Access being used as a “multi user databaseâ€, although, it certainly can be used as such, it is not a client server system, and never been designed with this use in mind.

Is this true? - the solution I'm being give is "not to use Access anymore"..

 

[Douglas J. Steele]

Yes, Access is multi-user.

All users must have Change control (RWXD) on the folder where the MDB file
exists, though. This is because the first user into the application must be
able to create the LDB file in that folder, subsequent users must be able to
update the file, and the last user out of the application must be able to
delete it. And no, you cannot have the LDB file written anywhere else.

--
Doug Steele, Microsoft Access MVP

(No private e-mails, please)

I've been using access for 8 plus years and have never had problems with

multiple people accessing the system (except if rights were not set up to
accommodate sharing on the server).

As long as the .ldb file was created in the same directory as the .mdb

file everything works great. In the past three weeks though I have had
multiple databases that are only allowing one user per time to access the
system even though the .ldb file resides in the directory. We now are
getting errors that say "mysysadmin" already opened exclusively.....

In talking to our network people I received the following messge:

Regarding Access being used as a "multi user database", although, it

certainly can be used as such, it is not a client server system, and never
been designed with this use in mind.

 

[Tony Toews]

In talking to our network people I received the following messge:

Regarding Access being used as a “multi user database”, although, it certainly can be used as such, it is not a client server system,

True, Access is not a client server system.

and never been designed with this use in mind.

Rubbish. I have a client running Access with 25-30 users just fine.

Is this true? - the solution I'm being give is "not to use Access anymore"...

Typical comments of arrogant IT departments who don't have a clue.
<wry smile>

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[John Flanagan]

What version of access are you using?
There are a couple of different possibilities that I know about and probably
quite a few more.

1. Someone is opening the db exclusively. Have a look at the ldb file next
time this happens and sort the nice person out.

2. In some versions of access the default open mode is exclusive. Make sure
everyone is opening the db through a shortcut specifying the full path to
the access program (?:\program files\...) as well as the path to the db.

HTH
John

I've been using access for 8 plus years and have never had problems with

multiple people accessing the system (except if rights were not set up to
accommodate sharing on the server).

As long as the .ldb file was created in the same directory as the .mdb

file everything works great. In the past three weeks though I have had
multiple databases that are only allowing one user per time to access the
system even though the .ldb file resides in the directory. We now are
getting errors that say "mysysadmin" already opened exclusively.....

In talking to our network people I received the following messge:

Regarding Access being used as a "multi user database", although, it

certainly can be used as such, it is not a client server system, and never
been designed with this use in mind.

 

[John Flanagan]

btw. Access is the bane of network admins lives.
It's very heavy on network bandwidth because as Tony Toews said, it's not a
client server system and throws large chunks of data across the network.
John

I've been using access for 8 plus years and have never had problems with

multiple people accessing the system (except if rights were not set up to
accommodate sharing on the server).

As long as the .ldb file was created in the same directory as the .mdb

file everything works great. In the past three weeks though I have had
multiple databases that are only allowing one user per time to access the
system even though the .ldb file resides in the directory. We now are
getting errors that say "mysysadmin" already opened exclusively.....

In talking to our network people I received the following messge:

Regarding Access being used as a "multi user database", although, it

certainly can be used as such, it is not a client server system, and never
been designed with this use in mind.

 

[Tony Toews]

btw. Access is the bane of network admins lives.

Oh? Why?

For incompetent, arrogant, uncaring network admins I can understand it

It's very heavy on network bandwidth because as Tony Toews said, it's not a
client server system and throws large chunks of data across the network.

More data than it should? Sure. Large chunks? I'd disagree with
that.

Yes, a client server system would be better but it comes at cost.
Increased complexity. Learning curve, etc.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm