Share problems in networked multiuser FE/BE database

[Steve Kendrot]

I have a split database on a peer to peer network(6 XP
computers). I have copied the front end to all 6 machines
and linked to the tables in the backend stored on a single
machine. I am having problems with multiple users
simultaneously entering data through forms. It seems to
work fine from any machine as long as it is the only user
with the database open. If two or more have the database
open at the same time, it opens other copies in read only
mode and will not allow new records or edits. I have
checked the form properties and both options for the
dataentry property. When set to yes, on anything but the
host computer, no records are shown in the form and new
records aren't allowed. I have tried importing the
required tables to the front end to make sure its not a
problem with my front end, and it works fine. Problem
arises when trying to access linked tables in the backend.
Help function hasn't given me any clues. Does anyone have
any suggestions. I had an access 97 version of this same
database with the same frontend/backend configuration set
up on a different network (Win 98) and it worked no
problem. Why would I have problems with Access 2002?
.

 

[jaydwest]

You might also check the default record locking (Tools | Options | Advanced). Make sure it is not set to All Records

 

[Steve Kendrot]

No luck

Pat,

Thanks for the advice. I checked the shared folders and unset the read only parameter. Did not, however, solve my sharing problem. I read an old post that suggested that if user level security is not set up, all users will open the database as ADMIN and thus the database will be opened exclusively on a first-come- first-serve basis. I'm thinking this may be my problem, as all of my record lock properties are set to allow sharing. Is there a way around this without setting up user level security (I've never done that and am a little gunshy). Is this a difference between Access 2002 and 97? Did not have this problem with 97 version of the database.

Thanks for your feedback.

Steve

 

[jaydwest]

Do you have one copy of the front end database that everyone users or does every user have their own front end database?

 

[Steve Kendrot]

Jay,

Each computer on the network has its own copy of the FE. I have 15 employees who share 6 computers. Based on yours and Pat's feedback, its sounds like I definately ned to incorporate User level security. Is it possible to set up just one user account that multiple people can share or will doing so create the same problem I am currently having with multiple users sharing the ADMIN logon.

Thanks for all your feedback. Any tricks I need to know or consider before implementing user level security?

Steve

 

[Steve Kendrot]

Back to business

Pat,

Thanks for your past feedback. I'm getting back to my database after a couple weeks of fieldwork. I have made some changes to my database and backed it up as you suggested. I copied it to my host computer on the Peer to Peer (where the BE is stored). I opened the database, ran the security wizard, and then ran the database splitter, thinking it would save me having to run the security wizard on both the FE and BE. My intention was to simply copy the FE to the other desktops on the P2P, but when I did, I ran into problems with the tables and forms opening in read only format. I have set full admin permissions for my admin workgroup "NuteBoss" but I still can't enter new data using the forms. Have I overlooked something simple?

I have a few questions I'd like to ask.

What is the most efficient way to get copies of the FE to the various workstations on the P2P?

Should each workstation have a copy of the workgroup file on its C drive, or is it acceptable to link to the workgroup file on the machine that hosts the back end?

If the FE is copied to each workstation, does the security wizard have to be run on each copy?

Does security wizard have to be run on the backend once the database is split even if it was run before the split?

Thanks in advance for your feedback.

Steve

 

[Steve Kendrot]

Back to business

Pat,

Thanks for your past feedback. I'm getting back to my database after a couple weeks of fieldwork. I have made some changes to my database and backed it up as you suggested. I copied it to my host computer on the Peer to Peer (where the BE is stored). I opened the database, ran the security wizard, and then ran the database splitter, thinking it would save me having to run the security wizard on both the FE and BE. My intention was to simply copy the FE to the other desktops on the P2P, but when I did, I ran into problems with the tables and forms opening in read only format. I have set full admin permissions for my admin workgroup "NuteBoss" but I still can't enter new data using the forms. Have I overlooked something simple?

I have a few questions I'd like to ask.

What is the most efficient way to get copies of the FE to the various workstations on the P2P?

Should each workstation have a copy of the workgroup file on its C drive, or is it acceptable to link to the workgroup file on the machine that hosts the back end?

If the FE is copied to each workstation, does the security wizard have to be run on each copy?

Does security wizard have to be run on the backend once the database is split even if it was run before the split?

Thanks in advance for your feedback.

Steve

 

[Steve Kendrot]

Pat,

Your feedback has been invaluable. I have spent the last couple days rereading the FAQ and browsing the AWF archives. You have the patience of a saint in answering questions that have been asked over and over. I apologize for asking them again.

Part of my problem is that I am VB illiterate so many of the solutions and work arounds are greek to me. I am having a hard time creating shortcuts that reference the appropriate workgroup file for the secured database. (My using workgrp admin to join the workgroup has resulted in all others appearing secured). I understand the concept, but I don't know how to force the shortcut to reference the appropriate mdw. The SecFAQ provides syntax (c:\msoffice\access\msaccess.exe /wrkgrp c:\myapp\secacc.mdw) to enter in the command line for the shortcut icon, but when I enter the syntax on the target window (by right clicking properties for the shortcut), it doesn't work. Maybe that's the wrong place.

I'm getting a farily good grasp of the whys, its the hows that have me flummoxed.

Steve