Re: Secured Database works exactly right on one computer, but on another not quite r
- From: "Rick Brandt" <rickbrandt2@xxxxxxxxxxx>
- Date: Wed, 29 Nov 2006 13:51:03 GMT
JessicaMorris wrote:
I set up user-level security on an Access 2003 DB on a Windows XP
machine, using the security wizard. I'm almost positive that I
tested it and it worked correctly at the very beginning.
However, at midnight before a presentation the next morning, I was
unable to edit the data. I already looked at lots of discussions,
and don't find anything quite like my problem. I'm fairly sure it's
set up properly, after having read several threads and looked at the
FAQ and also a better link to jmwild, since the FAQ isn't current for
2003. I have set up a similar one previously, except that the
'master' was actually the primary user's machine, and it worked
perfectly from the first moment.
On my machine, I am prompted for user id/password, and only those set
up are allowed. Some users are read only and some are full data. I
have a FE/BE set of DB's. The 'master' FE, BE, and mdw file are on
my Windows XP (completely current) machine. Only I have access to
the objects, which is correct, but no one, not even me or ADMIN can
edit or add data. All the other users can log on fine, but not edit
data.
In desperation, I copied the FE to my second Windows 2000/Office 2003
machine, from which I was planning to demo anyway, and it works
perfectly there! The first few times I copied the 'master' to the
second machine, I held my breath, afraid that it would not work, but
it always does. It really looks like it's the MACHINE, not the
setup, but I just don't see how that could be.
I've tried executing the 'good' copy across the network from my
machine...no good! However, if I connect remotely to that machine
and actually execute it on that machine from mine, it works
perfectly. But it's a pain in the neck to have to connect remotely
to the other machine, to test forms, etc. or just making minor edits.
My shortcut on the second machine is "C:\Program Files\Microsoft
Office 2000\ OFFICE11\MSACCESS.EXE" "C:\MAMG\MasterGardeners.mdb"
/WRKGRP "M:\Security. mdw". M: is mapped to the folder on my
machine. The data is linked to the BE on my machine. I realized in
researching this problem that I also need to join the BE to the
workgroup, but I'm waiting until I get this resolved. (Yes...I know
the path to Access says Office 2000, rather than 2003, but it was
upgraded and the existing office folder was Office2000; I didn't want
to tinker with changing the folder name. It is 2003.)
Can anyone help?
Thanks,
Jessica
What permissions did you grant users to the FOLDER where the file resides?
They need pretty much full permissions (file create, file execute, file
edit, file delete) or else Access cannot properly manage the locking file
(LDB) that allows multi-user locking to be controlled. If that file is not
created then edits are not allowed.
The reason that would affect you is once one person without file create
enters the app then everyone after that will also be read only because only
the first person to open the file can cause the LDB file to be created. If
you were the first person to open the file I would expect you to be able to
edit records.
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
.
- Follow-Ups:
- Re: Secured Database works exactly right on one computer, but on another not quite r
- From: JessicaMorris via AccessMonster.com
- Re: Secured Database works exactly right on one computer, but on another not quite r
- References:
- Secured Database works exactly right on one computer, but on another not quite r
- From: JessicaMorris
- Secured Database works exactly right on one computer, but on another not quite r
- Prev by Date: Secured Database works exactly right on one computer, but on another not quite r
- Next by Date: Re: More security questions
- Previous by thread: Secured Database works exactly right on one computer, but on another not quite r
- Next by thread: Re: Secured Database works exactly right on one computer, but on another not quite r
- Index(es):
Relevant Pages
|
Loading