RE: Local Copy: Will It Solve Read Only Problem?
- From: Robert T <RobertT@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 14 Nov 2007 08:32:01 -0800
Hi Jerry:
Thanks for the prompt response. I saw your suggestions on the Acess
setttings in another thread and previously changed them to comply with your
recommendation. That did not solve the problem.
In terms of read, write, and modify to a specific folder, the entire team
has the same exact rights so I don't think that's the issue.
Robert
"Jerry Whittle" wrote:
All users of the database must have at least read, write, and modify.
privileges to the folder holding the database file. Not just the database
.mdb file, but the entire folder. This is probably the problem. Also open the
BE database and go to Tools, Options, and Advanced Tab. Set the Default Open
mode to Shared and the Default Record Locking to Edited Record. (While you
are in the Options area, go over to the General tab and turn off Compact on
Close and Name AutoCorrect. Trust me on this.)
Copying the FE file to the user's computer probably won't fix the read only
problem. That's a network security issue. However putting the FE on the user
computers can really speed up the database as all the forms and reports are
on the hard drive and do not need to be pulled across the network.
You must run compact and repair in the BE if you want it compacted and
repaired. Don't go nuts over C&R. Once a month should be more than enough. A
few dozen MB's of bload is NOT a problem.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
"Robert T" wrote:
Hello:
I work for a govt. agency and developed a database that is split into an
application.mdb and a table.mdb. Obviously all of the tables are stored in
table.mdb. Both of them are on the same Network drive and each member of our
team has Access installed on their computer. However, if someone else opens
the database from the Network drive, everyone else gets READ ONLY access. I
thought splitting the database would resolve this problem, but it didn’t.
I’ve also followed everyone else’s advice to avoid this but it still happens.
Every Access book I read also said I should also install the front end
[application.mdb] on each local machine, however, no one explains how to do
such. Is that simply copying the application.mdb from the network drive to
each team member’s local hard drive [as opposed to a network drive]? Will
this resolve our READ ONLY problem when someone opens the application on
their local hard drive as opposed to the network?
And while I’m at it, let me ask a related question on splitting the
database. If I Compact and Repair the database while working in
Application.mdb, will that also compact all of the tables located in
Table.mdb? Or do I also have to run Compact and Repair from the database
where the tables are stored?
Robert
- Follow-Ups:
- Re: Local Copy: Will It Solve Read Only Problem?
- From: Pat Hartman
- Re: Local Copy: Will It Solve Read Only Problem?
- Prev by Date: RE: Setting up data to pull info from dates not stored in fields
- Next by Date: Table behavior (or design) problems
- Previous by thread: RE: Setting up data to pull info from dates not stored in fields
- Next by thread: Re: Local Copy: Will It Solve Read Only Problem?
- Index(es):
Relevant Pages
|
