Re: workgroup files and database splitter

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: skaufman (skaufman_at_discussions.microsoft.com)
Date: 01/13/05 

Date: Thu, 13 Jan 2005 12:53:05 -0800

Joan-

Thank you so much for the help. I went back to the original, and manually
split the database. The users are now being prompted for a password, and are
able to access. Yea!!!! The only problem I am having now is that when two
users are in, I receive the message "Cannot access, Admin file is currently
being used" . And then I get locked out. The Windows folder permissions are
all set correctly (read, write, create, delete... full permissions), and I
have two users set up, and assigned to workgroups: my user name has Admin
rights, and a billing user name has Full Permissions. Is there a reason why I
am receiving an Admin file error. Should I have set the users up differently?
Oh, the .mdw file is also in the same folder, and has full permissions,
including read, write, create, and delete. I really appreciate your
assistance.

Thank you,
Sharon

"Joan Wild" wrote:

> Hi Sharon,
>
> skaufman wrote:
> > I created a database (housed on a network drive) with a new workgroup
> > file. I then split the databases, having both on the share drive.
>
> How did you split it? If you used the database splitter wizard, then the
> backend will be totally unsecure. If you have the backup of the pre-split
> secure database, go back to that and split it manually.
> http://www.jmwild.com/SplitSecure.htm
>
> > Both dbases prompt me for the password, but when I go to someone
> > else's PC- I do not receive logon prompt.
>
> > If that's the case, then it isn't secured properly. That PC is likely
> joined to the standard system.mdw - they shouldn't be able to even open your
> secure mdb.
>
> > I read in one of the other
> > postings that I need to redirect my target path. I tried this, but
> > Access said that it could not find the file. I copied and pasted the
> > path that was in my shortcut. Is this not the best approach?
>
> You'll need to fix the problems above first, but post what you have in the
> shortcut. It's possible you are using mapped drives rather than UNC names.
> The two PCs may have different mappings.
>
> --
> Joan Wild
> Microsoft Access MVP
>
>
>

Quantcast