Using the Database Splitter with Password protection

[Stapes]

Hi

I created a database for a client some time ago which is password
protected, with it's own work group file. Then the client asked us to
split it. I used the Database splitter utility, and now my back-end is
no longer protected. How do I get it to share the same passwords &
permissions already assigned?

Stapes

 

[Joseph Meehan]

I suggest you start by reading
http://support.microsoft.com/default.aspx?scid=kb;[LN];207793

Access security is a great feature, but it is, by nature a complex product
with a very steep learning curve. Properly used it offers very safe
versatile protection and control. However a simple mistake can easily lock
you out of your database, which might require the paid services of a
professional to help you get back in.

Practice on some copies to make sure you know what you are doing.

Access 2007 as it doesn't support user-level security.

 

[Stapes]

Access 2007 as it doesn't support user-level security.

I am using Access 2003. What are you saying about Access 2007?

 

[John W. Vinson]

What are you saying about Access 2007?

That Workgroup Security was *REMOVED* from the product.

You can use a 2003-format database with its existing security, but if you
create a new .accdb format database, workgroup security simply isn't
available.

John W. Vinson [MVP]

 

[Joan Wild]

The database splitter wizard shouldn't be used on a secure mdb. As you've found, the resulting backend is completely unsecured. You should have split it manually. See www.jmwild.com/SplitSecure.htm

If it's too late to go back and redo, you'll need to open the backend while using the secure mdw (either use your shortcut you have now, login as a user you want to own everything, or create a new shortcut with "path to msaccess.exe" "path to backend" /wrkgrp "path to secure mdw")

Then create a new mdb, import everything from your existing backend, and proceed to secure it.

 

[Stapes]

The database splitter wizard shouldn't be used on a secure mdb. As you've found, the resulting backend is completely unsecured. You should have split it manually. Seewww.jmwild.com/SplitSecure.htm

If it's too late to go back and redo, you'll need to open the backend while using the secure mdw (either use your shortcut you have now, login as a user you want to own everything, or create a new shortcut with "path to msaccess.exe" "path to backend" /wrkgrp "path to secure mdw")

Then create a new mdb, import everything from your existing backend, and proceed to secure it.

--
Joan Wild
Microsoft Access MVP







- Show quoted text -

Hi

This is all very interesting. I also found this on the forum - which
solution seems to work:

http://groups.google.co.uk/group/mi...2a7d/42cceadbc5de2815?&hl=en#42cceadbc5de2815

Stapes