Packaging a VB app with an Access database 3

[VBRookie]

Hi,

I'm trying to package my VB application which uses an access database. I used the packaging and deployment wizard and it created a simple setup executable for me in the program files directory of my machine. When I go to that directory I see along with my program executable, my access database. Is there anyway that the access database can be hidden?

I don't want users when they install the app to be able to manipulate the data in the database directly. I want them to only be able to do it through the application. But if its right there in the program directory they can find it and delete it if then want to and then the app will return bugs when they try to use it.

Any help would be appreciated.
Thanks,
VB Rookie

 

[Hackster]

You can set the file attributes of the database to "Hidden", but anyone with a cursory knowledge of using the properties sheet can undo that. If you are really concerned about folks hacking around your database, I don't see a fool proof way of preventing it. After all, it is on their PCs. The only suggestion I would have is to do
a complete no-no and hard-code the DB path, then dump your database in a complex series of folders that are not attached to your app folder.

 

[animal]

What has worked for me in the past is to give your database a unique unassociated extention (ie. database.pef)

This way when they browse the folder and double click the file, access by default will not fire up and open the database. Of course, if they open the file in access, then all bets are off.

It's not high-tech, but it makes it more difficult.

 

[dotnetprogrammer]

VBRookie,
We have a commercial product, that uses an Access .MDB as part of the product. The users are mostly savvy MS Access users.
Our users can only access the database through the VB application. When we rolled out the product, the .MDB file went out with password protection. VB connection string has the password embedded. The .MDB can only be accessed and/or modified through the VB application.
I think the same will solve your problem.
Good Luck!

 

[VBRookie]

Thanks for your responses. The suggestions posted have been very helpful and I believe that I will soon have my problem solved.

Thanks again.

VB Rookie