RDLFC
asked on
Ms Access prevent queries from being exported
I have an access app that i have compiled to remove the code. however the passthrough queries are still visible if i attempt to import them from another access app. Is there a way to prevent the query and table objects from being exported?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
My guess is that what Scott posted will get you what you want,
You also need to ultimately consider your need for this.
Are you just trying t stop a casual user from clicking "Export"
Or are you trying to "Harden" the data from a determined hacker...
...or some other scenario?
The general rule is that "if they can see it, they can steal it.
vba automation, SQL Insert queries, Screeenshots, screenscrapers, copy/paste, cameras, even brute force memorization are all possible at some level,
"Is there a way to prevent the query and table objects from being exported? "
Well, if a user is already "in" the database, then they can use any number of technique to export it out...
I may have misunderstood your question here, so these are just some other things to consider.
;-)
JeffCoachman
You also need to ultimately consider your need for this.
Are you just trying t stop a casual user from clicking "Export"
Or are you trying to "Harden" the data from a determined hacker...
...or some other scenario?
The general rule is that "if they can see it, they can steal it.
vba automation, SQL Insert queries, Screeenshots, screenscrapers, copy/paste, cameras, even brute force memorization are all possible at some level,
"Is there a way to prevent the query and table objects from being exported? "
Well, if a user is already "in" the database, then they can use any number of technique to export it out...
I may have misunderstood your question here, so these are just some other things to consider.
;-)
JeffCoachman
You could add a Database Password to the file, and a user would need to know that password in order to open the database. Many times the developer will use a "launcher" application to open their password-protected database. The "launcher" app can be another access database the user opens, and then the launcher will actually open the password-protected database. This way, the user doesn't need to know the password:
Open in new window
Code poached from here: http://support.microsoft.com/kb/235422So your user would open the "launcher" app, and then the "launcher" app would run the code above to open your database. You could do this in the Open or Load event of a form to do things in an automated manner, or you could do this in the Click event of a button.