Database Security

[Aterlatus]

Hi all,

One of our clients recently approached me to ask for my assistance in sorting out a few bits and pieces on his access database. I've never really done anything in-depth in access before, but I do have a fair bit of database programming in a few languages / backends, so I said I'd give it a bash.

However, now he's sent me the database (2003 Database.mdb) I can't do anything with it! He's implemented security so all I have is user-level access. I can't seem to change anything

Could someone please advise me on how I can either:

a) Unlock the database that I already have to provide the design functionality

or

b) Tell me which files I need from my client to be able to access the design features for the database

Thanks

Steve Sherlock

 

[Norris68]

You will need a copy of their workgroup file (*.mdw) and a user/password combination. Use the workgroup administrator to join the workgroup (point it at the file). If the admin password is not blank you will be prompted to login when you open the database.

 

[psemianonymous]

Ask him for either/both the MDW file and the shortcut he uses to open the database (examine the command-line which will tell you exactly what MDW file he uses). If he is going to allow you access, you will need an admin-level username/password as well once you've got it set up to work on your machine--either his username/pw or a new one.

 

[Aterlatus]

Well, the shortcut he uses points to:

"C:\WMP Services\Invoice Database 2003-4\2003 database.mdb"

Does that mean he's using the default system.mdw?

Is there any way to bypass this security, so I don't have to request the file from him, or do I *HAVE* to have that file, even if the admin password is blank?

Once I've obtained the file, how do I "attach" it to the database so I can get at the design functions?

Thanks for the speedy reply

Steve Sherlock

 

[psemianonymous]

yes, he's using his default system.mdw, OR he's using some hidden "development-only" MDW file(*). You have two options:

1. Get his system.mdw file from his computer, rename it and add it to the shortcut like so:

"C:\Program Files\Microsoft Office\MSACCESS.EXE" "C:\WMP Services\Invoice Database 2003-4\2003 database.mdb" /wrkgrp "c:\temp\mynew.MDW"

or something to that effect. Note that you may *still* need a username/password to get into the database, assuming he has set things up semi-properly.

Best-case scenario using this method is that when using hte new workgroup, you will open the database with full priveleges (sp?) with no problems, just like any other (unsecured) database.



2. See how good his security is. Try and bypass it by opening a new database and importing all his objects into the new one. This might work if he hasn't set everything up right. Also note that when importing, click on Options>> and select ... well, select everything available for importing.
This option will strip out all his security permissions, but that's his problem--he didn't set it up properly.

Best-case for this is that you are able to import all objects and the database runs fine. I believe you lose some advanced options such as the startup features (Tools->Startup), but most things are imported. Also, he loses his special security, which is probably a bad thing.



* - It is possible that he has set up the security so that by default everyone gets user-level security but to edit the design you must have proper security, which he holds. This doesn't seem likely from your description, but it's possible.

 

[RickSpr]

In addition to the security permissions and the Startup options, you will also lose the References collection and the VBA Project properties (project name and description, conditional compilation arguments, help file name and project context ID, etc.).

Rick Sprague
Want the best answers? See faq181-2886
To write a program from scratch, first create the universe. - Paraphrased from Albert Einstein

 

[Aterlatus]

Yeps - the importing thing seems to have worked - I should at least be able to iron out the bugs he was having now without having to grab his mdw, even if I need it to stick the fixes in

Thanks guys.

I'm sure I'll be posting back here soon to find out how I *can* implement some decent security on this database