I scan old newsgroup postings for those that have only their initial
inquiry, to determine why no one bothered to react to your question, issue,
or concern. If you have not already resolved your "Requiring a code/password
to use mdb" problem, I have a suggestion.
Of course, you could always set up Access security. At its maximum
capability, you'll have to set up user Workgroups, assign passwords and
permissions. This is good when you have a generally captive audience (like,
on a LAN), but if the number and variety of users is variable, you'll need a
cadre of data input clerks to keep updating the security protocols with every
new user or at the time that you need to update access to Access (say,
monthly as you mentioned in other, similar postings).
An easier way would be to impose security programatically. Build a
form that opens when Access is started and have a generic password that the
user must enter before the remainder of your system is allowed to operate.
That way, each user uses the same password and they only get that [monthly]
password when they re-register for another month's worth of play-time. Using
this method, you only have to change the internal "password" monthly and only
give that password out to your valid subscribers. If you make the monthly
password complex enough, you'll virtually eliminate "hackers."
There are a number of articles discussing security practices in the
Microsoft Knowledge Base. Log onto
www.Microsoft.com and start searching.
Steve in Ohio
