Question Password protected back end

[niak32]

Hi again !

I am trying to protect a back end of a database that i am creating with a password. I used "Set database password" on the back and it works great.

What i am having problems with is making the front end (which still has the tables linked to the password protected back end) connect to the back end with out the user typing in the password.

Sounds kind of silly but i want at least this level of security so no one can play with the back end directly.

After looking through the forums and a lot of googleing there are HEAPS of references to connectionstrings.com. My problem is, I don't know how to do any of it. In a module? macro? on each and every form? not sure and my tests have failed.

Any help would be appreciated.

 

[Banana]

I suppose it depends on what you are using password for.

If it's a simple corraling system and you just want to keep honest users honest, then you could just store the password hidden in the database and use the connection string to fill the password argument.

If it's more of a simple deterrence to computer savvy user who are too curious for their own good and you're using MDE/ACCDE, then you can generate a password based on components of database (e.g. piecing together random bits and ends of properties and objects and make it a password). Because the algorithm used to build the password will be compile, it will be difficult to decode what it actually and more so if you don't merely just concatenating but perform various operations (e.g. addition, subtraction, multiplication of the hexadecimal representation of the various bits & ends).

If it's primarily for malicious hackers or disgruntled employee wanting to torch down the company, then it's wrong security mechanism for the job.

 

[niak32]

Thanks for the reply Banana.

I ended up relinking the tables and i could insert the password there and not have to do it again. Don't know why I couldn't find the info how to do that online (although it did seem quite obvious after i did it).

I would love it if i could find a good tutorial about database protection that does not rely on the group permissions etc Using algorithms to generate and set a password would rock, Since I am just trying to protect my product from semi tech "Oh, I'll just change this bit, that will make it better !" people, I think the password on the back end is good enough for now.

Any links to custom security you can dig up, hopefully made for noobies would be fantastic.

Cheers

 

[Banana]

Jack MacDonald's How I use User Level Security