Protecting Database frm being Imported into a new Database

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

Guest

Hi,

I've written an Access database using XP, but converting it to 2000 so my
collegues can use it on older MS versions, and while i want users to add data
to it I don't want them accessing Forms, Queries and reports in Design View.

I've secured the main switchboard by creating a module that stops bypassing
by using the Shift key on entry. My problem lies in that anyone can open a
new database, copy my original and then has access to my queries, forms etc.

I'ver followed the suggestions on both Jack Macdonalds and Joan Wilds
brillaint web pages but in my frustration must have missed some steps. I
have changed ownership of every thing to my "Super User" and tried numerous
attempts at different permissions

Also I found that by stopping all the Users permission they can't get into
the database at all.

I've looked at MDE files (allbeit fleetingly) but can still import them into
a new database and have total access.

Any help would be really appreciated

thanks

Annette
 
The permissions that you set on forms, reports, etc in an MDB file can
prevent the user from modifying them INSIDE that particular MDB, thus
preserving the integrity of the application program. Furthermore, you
must allow the users to have Read Design permission for them to open
the reports or forms. Accordingly, users can see the design of the
form, but cannot modify it. For many situations, this amount of
protection is sufficient.

However, users can create a new database, import an object, and play
with it in the new database. Non-privileged users cannot return
modified objects to the original MDB file.

In order to prevent the user from seeing the object designs, you must
create an MDE file -- the MDE strips all the viewable stuff from the
file, leaving only the "executable" components. Thus, the user is
unable to see the design, much less modify it. If you want to preserve
the secrecy of your design, you must create an MDE.

You cannot make an Access 2000 MDE using Access XP - you may only
convert the XP-MDB into a 2000-MDB. If you want to hide its design,
you must use Access 2000 to create a 2000-MDE.

Lastly, I presume you have split your database into FE and BE
components. Apply the appropriate permissions to the BE to protect the
integrity of your data. Convert the FE to an MDE to preserve the
secrecy of your form and report designs.




Hi,

I've written an Access database using XP, but converting it to 2000 so my
collegues can use it on older MS versions, and while i want users to add data
to it I don't want them accessing Forms, Queries and reports in Design View.

I've secured the main switchboard by creating a module that stops bypassing
by using the Shift key on entry. My problem lies in that anyone can open a
new database, copy my original and then has access to my queries, forms etc.

I'ver followed the suggestions on both Jack Macdonalds and Joan Wilds
brillaint web pages but in my frustration must have missed some steps. I
have changed ownership of every thing to my "Super User" and tried numerous
attempts at different permissions

Also I found that by stopping all the Users permission they can't get into
the database at all.

I've looked at MDE files (allbeit fleetingly) but can still import them into
a new database and have total access.

Any help would be really appreciated

thanks

Annette
Click to expand...


**********************
(e-mail address removed)
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security
 
Back
Top