Multi user problems in Access 2003

[Guest]

I have a client with an Access DB I created. Originally it was in Access
2000. Recently they client migrated to Office 2003. I migrated the database
to Access 2003. I have checked and rechecked that it is set to open in
Shared mode, has macro security set to low, have auto correct turned off.
Since we switched to Access 2003 only one user at a time can use the
database. I get a variety of messages - usually Error 3734 Passive
Shutdown/Connection problem or that the database has been put in a "state"
that prohibits other users. Can anyone help with this issue? I am ready
to take the database back to Access 2000.

Thanks - Margaret

 

[Graham Mandeno]

Hi Margaret

Whatever version of Access you are using, you would be strongly advised to
split your application into a backend (linked data tables) and a frontend
(everything else) if you have multiple concurrent users.

Frankly, you have been lucky if you've managed to run multi-users in Access
200 without problems.

See Tony Toews very good coverage of the subject here:
http://www.granite.ab.ca/access/splitapp/index.htm

 

[Guest]

Hello,

Thanks for the response but splitting the database into a front- and
back-end did not change anything. I am planning to make other changes to the
database but can't do much until the multi-user issue is resolved.

Hi Margaret

Whatever version of Access you are using, you would be strongly advised to
split your application into a backend (linked data tables) and a frontend
(everything else) if you have multiple concurrent users.

Frankly, you have been lucky if you've managed to run multi-users in Access
200 without problems.

See Tony Toews very good coverage of the subject here:
http://www.granite.ab.ca/access/splitapp/index.htm

--
Good Luck!

Graham Mandeno [Access MVP]
Auckland, New Zealand

I have a client with an Access DB I created. Originally it was in Access
2000. Recently they client migrated to Office 2003. I migrated the
database
to Access 2003. I have checked and rechecked that it is set to open in
Shared mode, has macro security set to low, have auto correct turned off.
Since we switched to Access 2003 only one user at a time can use the
database. I get a variety of messages - usually Error 3734 Passive
Shutdown/Connection problem or that the database has been put in a "state"
that prohibits other users. Can anyone help with this issue? I am
ready
to take the database back to Access 2000.

Thanks - Margaret

 

[Guest]

Hi Margaret,

When you ran the split DB test, did you make sure that each user had a copy
of the front-end (FE) database installed on their local hard drive? If you
simply split the DB, but people accessed the same common FE file, then this
test is not valid.

Make sure that all users have the latest updates for their version of the
Windows Operating system, their version of Office, and the JET database
engine. Use this KB article as a guide:

How to keep a Jet 4.0 database in top working condition
http://support.microsoft.com/?id=303528

In addition, you should make sure that all users have MDAC 2.8 (Microsoft
Data Access Components) installed:

How to check for MDAC version
http://support.microsoft.com/kb/301202
and
http://msdn.microsoft.com/data/ref/mdac/downloads/

Here is a paper that I wrote that you may find helpful:

Implementing a Successful Multiuser Access/JET Application
http://www.access.qbuilt.com/html/multiuser_applications.html


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Guest]

Hi Tom,

Thank you very much for your detailed reply. I am meeting with the client
and network consultant this morning. I will review many of the settings and
see how things improve. Thanks again.

Margaret

 

[Guest]

My delayed reply?

Please know that everyone who answers questions does so on a voluntary
basis, as time allows. The high majority of the answers (probably > 99.5 %),
are posted by people like myself, who do not work for Microsoft.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Guest]

Oh geez!

I haven't had my first cup of coffee yet. Somehow I read the word "detailed"
as "delayed". I apologize for that!


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html

 

[Guest]

Thanks for checking - at first I was a little confused by your reply. Your
information was helpful. It seems that the solution was to 'uncheck' all the
startup options in the startup menu. Even though the database was set to be
shared (not exclusive) allowing tool bar changes etc seemed to put the
database in a very secure exclusive mode. I don't really understand but it
seemed to solve the problem so that everyone could get their work done.

Thanks again.

 

[Guest]

Hi Margaret,

There's lots of actions that a user can take that will look like changes,
such as toolbar changes or applying filters in forms. That's one of the
reasons it is important that each user be working with their own copy of the
front-end database.

http://www.access.qbuilt.com/html/gem_tips1.html#SplitDB


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________