Limiting View to Forms and Reports

[Guest]

Is there a way that I can set up access so no user can view items behind the scenes in Access? I have it set up so there's a start screen and the database window is hidden, but people have gotten wise to open their Database utlizing the shift key. Is there a way to prevent users from doing this and viewing items behind the scenes from the forms? I hope I didn't confuse anyone with the question, its early ha.

 

[Wayne Morgan]

You may want to start by giving the use and mde file instead of an mdb file.
Make sure you keep a copy of the mdb for yourself so that you can make
modifications in the future. You can't modify an mde and can't create and
mdb from an mde, you MUST keep an mdb as a backup and for futer
developement.

--
Wayne Morgan
MS Access MVP

Is there a way that I can set up access so no user can view items behind

the scenes in Access? I have it set up so there's a start screen and the
database window is hidden, but people have gotten wise to open their
Database utlizing the shift key. Is there a way to prevent users from doing
this and viewing items behind the scenes from the forms? I hope I didn't
confuse anyone with the question, its early ha.

 

[Guest]

I thought of this as a solution, the database is fairly large on both ends, information and tables on one, and queries, forms, reports and macros on the other. I have no trouble making the .be database an mde file, however the production database doesn't produce an mde. It always tells me that it cannot be made an mde. Any suggestions on how I could make this happen?

 

[Wayne Morgan]

I probably wouldn't make the back-end an mde, just the front-end. There are
some things that will keep an mdb from being made into and mde.

1) If there is any code that won't compile, since and mde is compiled code
only. All the text code is removed. Go to the VBA window then
Debug|Compile... and try to compile the database. Fix any errors returned.

2) I have seen this problem when trying to save the mde to a network share
using a UNC path. To get around it, I saved it to a local path then copied
it.

What is the exact error you receive?

Compact and repair the database before you do this. It is a good idea to do
this on a regular basis anyway (both front and back ends). You have to have
exclusive access the the database in order to do this. Also, place a copy of
the front-end on each users computer, don't have them share a single copy
from the network share.

Also, here are some articles that may help:
http://www.mvps.org/access/bugs/bugs0020.htm
http://www.mvps.org/access/modules/mdl0022.htm
http://support.microsoft.com/default.aspx?scid=kb;en-us;289686&Product=acc2002

--
Wayne Morgan
MS Access MVP

I thought of this as a solution, the database is fairly large on both

ends, information and tables on one, and queries, forms, reports and macros
on the other. I have no trouble making the .be database an mde file,
however the production database doesn't produce an mde. It always tells me
that it cannot be made an mde. Any suggestions on how I could make this
happen?