Security for a project that uses Access DB


I've crated an app in VB6 that uses a DB made in Access 2000 (with DAO 3.6).

I don't wan't let users see or change any data on the DB using Access (or any other DBMS if possible). I want this DB to be manipulated only through my app.

I've set DB and user passwords from Access, but there are programs (even free) on internet that can show these passwords easily.

So what can I do to make more difficult to open and manipulate this DB?
LVL 13
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Unfortunately, because of the easy password finding tools for Access, they simply do not do a good job of protection.  Your best option is to probably encrypt the data in the database that is sensitive, and use your app to encrypt/decrypt before writing/reading from the database respectively.
Yes, you can try to encrypt your database. Or, else you can just rename it yo somename that people wonn't notice like system_10.dll

~ fantasy ~
If you're dealing with an OS (NT, 2000, XP) that supports fule/directory permissions, you may be able to set things up so that only your application has permission to access the file.  See:
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

rettiseertAuthor Commented:
Encrypting data sounds good, but speed is very important for my program. Thanks.

I've already renamed my DB, but the LDB generated when a MDB is open let users know that the file is a standard Access DB.

I did't know I could set permission this way. Unfortunately the program must work on any Win32 enviroment (from 95 to 2003).

I was thinking... what about using hidden autoexec macros in Access and hidding the tables makind them System tables?
rettiseertAuthor Commented:
Thanks to all
As long as your database is on the server, it doesn't matter what OS the user has.  If the database is on each individual user's system then encryption may be your only alternative with Access.  You seem to be assumint that someone is going to be motivated enough to hack your data.  If that's the case and it has to reside locally on the client machines consider using MSDE.  Then, you'll essentially be using SQL Server which is a more secure system.
rettiseertAuthor Commented:
Yes, the users will be motivated to to crack this database.

In most cases setting passwords and renaming will be enough, but not always...

I haven't used SQLServer, so I don't know if I need to do many changes to my code and if a SQLServer DB file(s) can be distribute freely with my program.

Thanks again.
What solution was used in the end?
rettiseertAuthor Commented:

1-Renaming database
2-Autoexec macros in access to block the program
3-Hidding tables to make them system tables

I guess encrypt is the best method, but as I said, speed is very important for this project.

Thanks again AzraSound and all the others...
Wel, you're always going to face tradeoff of course.  It's drastic but there are quite a few freeware encryption components and programs available.   I'm pretty sure you can have your code in one file access data in another .mdb - perhaps attatching the tables I don't remember.  At any rate, You could encrypt the whole data .mdb file and have your code call the encryprion dll or shell the application and decrypt it.  Reverse the process when your application ends.  I don't know what the speed would be, depending on the size of the data .mdb but the decryption/encryption would only happen once at startup and shutdown.  You'd be working with regular data the rest of the time.  The only time they'd have access to the unencrypted data would be during your application's runtime and if you grab an exclusive lock then they couldn't open it then, even using Access.  They could ctrl-alt-delete and kill your application which would leave the data unencrypted.  If they tried to look at the encrypted .mdb otherwise, they's get an error which should discourage prying.  No solution is perfect but some form of encryption is probably the best you can do.
PAQed, with points refunded (60)

Friendly Neighbourhood Community Support Admin

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.