On 16 Oct 2003 15:17:55 -0700,
de**********@snclavalin.com (Struggling
Coder) wrote:
One more example of how important it is to have good documentation.
If the database is properly secured with Access-level security, you
need to be able to recreate the system.mdw in order to get complete
access to the objects. At least you need a userid, password, and PID
of a user with administer rights. Your former employee may be able to
give you that, provided you can find this person, and he/she remembers
or has better documentation than you do.
Fortunately properly securing a database is hard, and a good line of
attack is to find vulnerabilities in the application of security in
this instance. Securing an app is a multistep process, and one can
easily forget a step, resulting in less-than-perfect security. It all
starts with having a THOROUGH understanding of Access-level security.
Download, study, and fully understand the Access Security FAQ from
Microsoft. DO NOT click around in the security options until you
absolutely know what you are doing. Use a copy if you can't resist.
-Tom.
We have a database here at work and the person who created has been
gone for two years. The original project manager wants to use this
database on his New project, but the database is secured. I can get in
to the database using the shift key, but all the objects are secured.
I checked the users and all that show up are "admin" & "user". I
guess that's what is in my SYSTEM.MDW. I can not retrieve the original
MDW file because his computer is long gone.
The user was not hired to write software, but developed this database
for the company, and also signed an intelectual property agreement
upon hiring on with this company.
Is there a way to get into this database so we can set it up for use
on his new project?
