Jst

JST

Registered User.
Local time
Tomorrow, 02:30
Joined
Feb 12, 2016
Messages
18
Hi,

I have some 50 queries, 20 reports and 30 macros all related to 2 Tables. This MSACCESS database is being used by several users installed in 3 systems. I want that nobody should be able to see my Queries, Reports and Macros. I have set all objects as hidden. I have also hidden the navigation pane, tool bar and disabled the F11 function key using the VB code in the form.
Now the problem is that although, no one can have access to any object in this particular database, but the user can always import any of the objects in a blanks database. Even the hidden objects can be copied by checking the "Show hidden files" box in the blank database.

Is there a way by using some code, so that the hidden objects do not appear in the import function.
 
Thanks Ranman. I have tried this also. But if you open a blank database, you can still import objects from a ACCDE file in ACCESS2010
 
Nope, no way to stop that. Hiding doesn't mean hiding from Access itself.

May I ask what the secret is? What exactly are you trying to keep people from finding out?
 
Hi Gina,
Primarily 2 reasons
I want to have full control and
2. The staff is novice to Access and keep on fiddling with queries/ reports creating problems for me.
I was working in FoxPro earlier and was very comfortable with .exe file. Wonder if Microsoft strengthens MSACCESS in a similar way.

Regards
 
Hmm, then split the file and have a Master file. If they fiddle with it they only mess up their front end. AND, when you distribute updated front ends all their fiddling will be lost. That's as good as it gets with Access.

Oh, no... never heard of any mention to make .EXE's. If you want that much control move to .NET.
 
Thanks Gina. Will try this and revert. Alternately, is there a way out to keep the main Form in a seperate database.
Regards
 
google for creating .exe for ms access (i think its orlando's site).
 
If what you mean to say is an executable file (.accde), I have tried that also. You can still access all the objects.
 
have you really tried?
 
Not sure what you mean by *keeping the main form in a separate database*. If it is a form your Users need than it will be in their front ends which is separate.
 
Yes Gina. I mean to have the front end form in a separate database. I succeeded somewhat by having 2 .accdb files A & B, where file B is the main database file. I set the reference of file B in A. Write a module in B to open form (to be used as front end). Now you can access this module in database A.

Having done all this, the problem remains that when A opens it asks for the password (of B, since it has reference) and this password can be used in any blank database to import objects from your file B.

And everything returns back to square one.
 
Just seems like a lot of work for little gain since they can still get their hands on the Objects anyway. You do know the lock is only to keep the honest guy honest, the thief is coming in no matter what...
 
very true. And my problem remains a problem.......

thanks anyways for sharing your thoughts.
 
thanks Arnel. The idea appears to be wonderful. The DBtoEXE coverter app is not working in my office laptop. Will give it a try at home with my personal laptop.

regards
 
I just had a look at that... never seen that before so I guess I'll play!
 
Many thanks Arnel. The exe has really worked. I am able to protect my entire database.

regards.
 
i have no idea, you should address that to the author since that is his site.
 

Users who are viewing this thread

Back
Top Bottom