Multi User Access (2003)

[Trevor Aiston]

I've just had Access 2003 intsllaed on our new admin assiatnts PC.

But when she is using a database I cannot access it. Message says 'The
dabase has been placed in a state by user admin on machine xxxxx the prevents
it from being opened or locked'

We've never had problems with multi user access before.

ANy ideas

 

[aaron.kempf]

if you want Multi-User Access 2003, then you need to _UPSIZE_ to SQL
Server and 'Access Data Projects'

 

[Tony Toews [MVP]]

if you want Multi-User Access 2003, then you need to _UPSIZE_ to SQL
Server and 'Access Data Projects'

Completely wrong.

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[aaron.kempf]

how is it wrong? Jet corrupts-- so I stopped using it.
Jet isn't stable enough for a single user nor a single record.

Jet doesn't run over wireless, VPN, WAN-- Jet just doesn't work over
any network.

**** Jet in the mouth.
And anyone else that bullies anyone on this newsgroup that thinks
differently.

It's called 'USENET'.
And you can't dictate what is on here you fat lazy ****.

-Aaron

 

[Jamie]

I have been reading through this thread because I have the same problem. I
have been using Access for a number of years and have always been able to
correct this problem - well not this time. The database on the server under
tools/options/advanced is marked as shared with record level locking on the
record being edited. Won't fix the problem. I have even tried to create a
new database then copy all of the objects from the old database to the new.
Get the same error. It is probably something that I am doing, but I sure
don't know what it is. Any suggestions would be appreciated. Using verson
2003 with latest updates.

 

[Tony Toews [MVP]]

I have been reading through this thread because I have the same problem. I
have been using Access for a number of years and have always been able to
correct this problem - well not this time. The database on the server under
tools/options/advanced is marked as shared with record level locking on the
record being edited. Won't fix the problem. I have even tried to create a
new database then copy all of the objects from the old database to the new.
Get the same error. It is probably something that I am doing, but I sure
don't know what it is. Any suggestions would be appreciated. Using verson
2003 with latest updates.

Are you sharing the FE among multiple users? Have you split the
database file into a FE and BE?

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Tony Toews [MVP]]

F*** Jet in the mouth.
And anyone else that bullies anyone on this newsgroup that thinks
differently.

It's called 'USENET'.
And you can't dictate what is on here you fat lazy f***.

I'm not the one doing the bullying or using foul language.

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Jamie]

Tony thank you for responding.

No the database is not split. I work in a small office and only two people
access this database. However, the database is used frequently by these two
people.

 

[Tony Toews [MVP]]

Tony thank you for responding.

No the database is not split. I work in a small office and only two people
access this database. However, the database is used frequently by these two
people.

In my opinion you've been lucky but now you got bit. Splitting the database will
likely stop this error from occurring in the future.

See the "Splitting your app into a front end and back end Tips" page at
http://www.granite.ab.ca/access/splitapp/ for more info. See the Auto FE Updater
downloads page http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. The utility also supports Terminal Server/Citrix quite nicely.

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Jamie]

I'll do that. Thanks.

In my opinion you've been lucky but now you got bit. Splitting the database will
likely stop this error from occurring in the future.

See the "Splitting your app into a front end and back end Tips" page at
http://www.granite.ab.ca/access/splitapp/ for more info. See the Auto FE Updater
downloads page http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. The utility also supports Terminal Server/Citrix quite nicely.

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/