workgroup files and database splitter

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

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. Both dbases prompt
me for the password, but when I go to someone else's PC- I do not receive
logon prompt. 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? Do I need to re-merge the database to resolve this? I appreciate
any assistance.

Thank you.
Sharon
 
Hi Sharon,
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.
Click to expand...

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.
Click to expand...
If that's the case, then it isn't secured properly. That PC is likely
Click to expand...
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?
Click to expand...

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-

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
 
skaufman said:
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.
Click to expand...

First, your users shouldn't be using the same copy of the frontend on the
server - give them a copy on their PC (linked to the backend on the server).

Also ensure that the mdw is not named the same as the backend mdb, as each
file needs to create their own ldb.
 
Joan-

Thanks for the quick reply. When I copy and paste the front end dbase onto
someone's hard drive, how does the security stay with it? I tried it, and the
user is no longer being prompted for a password. I also tried having two
users in at the same time, and I am being told the back end dbase is in use
for the one that entered the database most recent. Does the .mdw file have to
be on their hard drive as well? I think I am missing some step, but I'm not
sure. Oh, the mdw and mdb are not named the same.

Thank you.
Sharon
 
skaufman said:
Joan-

Thanks for the quick reply. When I copy and paste the front end dbase
onto someone's hard drive, how does the security stay with it?
Click to expand...

Permissions are stored in the mdb file (the mdw contains the
usernames/passwords/groups/membership information).
I
tried it, and the user is no longer being prompted for a password.
Click to expand...

Go back to my initial response. In there I said it sounded as though you
hadn't secured it properly, and that is still the case. You've missed a
step in applying security. Users should *only* be able to get in if they
use the proper mdw file. You need to start over.

Try the steps outlined at
www.jmwild/com/AccessSecurity.htm
I
also tried having two users in at the same time, and I am being told
the back end dbase is in use for the one that entered the database
most recent. Does the .mdw file have to be on their hard drive as
well?
Click to expand...

That could be be left over from your previous problem. Get everyone out of
the mdb and see if the ldb file is still in the folder where the backend is.
If you see it, delete it. Ensure that all users have full permissions
(Windows permissions) on the folder where the backend is.

I would not recommend putting the mdw on their hard drive, as that will be a
nightmare to maintain.
 
Joan-

Thank you again for all your helpful suggestions- I have gone to your
website, and printed the instructions. I will test them out. Thanks again.
 
Back
Top