MDE File - queries, tables.

[AJ]

Is there anything you can do to a MDE file to prevent users from
chnaging/modfying queries or tables?
I wrote some of my reports, etc. based on queries and am worried that they
might accidently alter the query.

Any advice how others have handles this?

 

[Allen Browne]

It is possible to block people with Access Security, though this is probably
overkill. Also, I can't recommend that approach, since MS has removed it
from the new file format in A2007.

One simple idea is to use attached tables. This has lots of advantages, one
being that users can't just change the table: they have to figure out where
the back end is, and open that. If splitting is a new idea, see:
http://allenbrowne.com/ser-01.html

Another suggestion is to turn off Special Keys (so the user can't just open
the Database window), and never display a table or query directly (so user
cannot shift it to design view.) Custom menus/toolbars can also make it
harder for users to find design view for anything. Set AllowBypassKey to No
as well. That's enough to keep the average nosy punter out.

One of the crucial things here is whether you really want to take on the
responsibility for this kind of thing. IME, small business people (the usual
Access audience) are scared of messing up their database: they really don't
want the expense and loss of functionality.

For cases where power users could validly be messing with queries, I tend to
create a 2nd front end. This is an MDB, linking to the same tables, but
without any forms/reports. In this database, they can destroy their data
(again, their problem), but they won't harm your application.

 

[Albert D. Kallal]

Is there anything you can do to a MDE file to prevent users from
chnaging/modfying queries or tables?
I wrote some of my reports, etc. based on queries and am worried that they
might accidently alter the query.

Any advice how others have handles this?

I useally just hide the interface......

You most certainly can, and should hide all of the ms-access interface. The
options to complete hide and keep people out of the ms-access interface can
easily be done using the tools->start-up options. Using those options allows
you to complete hide the ms-access interface (tool bars, database window
etc). Also, using these options means you
do not have to bother setting up security.

Try downloading and running the 3rd example at my following web site that
shows a hidden ms-access interface, and NO CODE is required to do
this....but just some settings in the start-up.

Check out:

http://www.members.shaw.ca/AlbertKallal/msaccess/DownLoad.htm

After you try the application, you can exit, and then re-load the
application, but hold down the shift key to by-pass the start-up options. If
want, you can even disable the shift key by pass. I have a sample mdb file
that will let you "set" the shift key bypass on any application you want.
You can get this at:
http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html

If you thus convert that mdb into a mde, and also lock out the shift key,
then users will never see, or even have to know this is a ms-access
application.

Try the above sample.....

 

[Tom Wickerath]

Hi AJ,

Disable the option under Tools | Startup, for displaying the database
window. Make sure to provide a startup form, specified via Tools | Startup or
by using an Autoexec Macro. Then disable the Shift Bypass key, so that a
person cannot open the database directly to the DB window. See "By Pass Shift
Key Code", here:

http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html

These moves will make it a bit more difficult for others to get in, but it
certainly won't stop knowledgeable users.

Consider implementing Access MVP Tony Toews AutoFE updater with a split
database. If you specify the %AppUser% folder, and distribute a shortcut to
each user, each person's copy of the FE (front-end) file will be saved to a
normally hidden folder.

http://www.granite.ab.ca/access/autofe/gettingstarted.htm


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[John W. Vinson]

Is there anything you can do to a MDE file to prevent users from
chnaging/modfying queries or tables?
I wrote some of my reports, etc. based on queries and am worried that they
might accidently alter the query.

Any advice how others have handles this?

Implement Workgroup security and lock down design mode on everything.

Microsoft Access 2000 Security FAQ:

http://support.microsoft.com/kb/207793/en-us

Read it carefully; follow it precisely. It's easy to mess up security!

John W. Vinson [MVP]