By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,662 Members | 1,790 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,662 IT Pros & Developers. It's quick & easy.

Access security

P: 1
I was successful in creating a MDB that could be installed on a standalone computer and once installed could not be copied to another computer. The method used was to have code that made WinAPI_GetComputerName call and stored the computer name on the database, the first time run.

That was good up until now. Now I have a request to have it installed on a network. Is there any technique that I can use to prevent a copied MDB file from the server from executing on another computer? Apparently the WIN API I am using gets the computer name from the machine running the code.

Any ideas/techniques would be appreciated.

Cheers,
Boris
Jul 26 '07 #1
Share this Question
Share on Google+
1 Reply


MMcCarthy
Expert Mod 10K+
P: 14,534
Creating a login procedure which checks NTUser name is the best way. The names can be stored in a table and if the logged in user is not in the table then the database can close.

This is better than the physical computer as you will run into maintainability problems if a computer is upgraded or changed for any reason.
Aug 6 '07 #2

Post your reply

Sign in to post your reply or Sign up for a free account.