Linked table with variable password: verification of password doesn't work ?!

[CPBV]

Hello all,

Since security is not something I can do easily (someone
will do the job in november), but I do need sóme sort of
security soon, I have created an external database with
the variables DATA_ENTRIST (name of the person who does
the data entry), LOGIN (initials of data entrist) and
PASSWORD (password for the specific data entrist).
{Ofcourse, for multiple data-entrists, thus having
multiple names, logins and passwords.}

In the actual database where data entry needs to be done,
I have created a kind of start form, which asks for the
name, login and password of the data entrist. I have
programmed a the following validation rule: "[External
database].DATA_ENTRIST=DATA_ENTRIST" and "[External
database].LOGIN=LOGIN" and "[External
database].PASSWORD=PASSWORD", and the validation
text: "Your login or password is not correct !"

However, it doesn't work ! When I fill in the start form
with data that occur in the external database, I keep
getting the validation tekst. What am I doing wrong here ?

Thank you in advance !!!

 

[Jeff Boyce]

You have an "external database" with three fields holding your valid
combinations of data_entrist, login, and password. How does Access, via
your form, know which row to test against?

 

[CPBV]

Hello Jeff,

You have a good point there ! Ofcourse Access doesn't know
which row to test against... I didn't think of that. That
must be the problem then. But: how can I solve this
problem ???

Anyone ?

 

[Jeff Boyce]

General concepts:

collect user info on form (unbound)
run a query against the table to see if there's a match
if there is, they pass
if no match, send them back through the "logon" form/process again
decide how many times they get to try before the application shuts down

 

[Chris Nebinger]

Might I suggest a path that you have not considered?

Using the code found on www.mvps.org/access/api, capture
the user's network login name. Validate this name against
your table of authorized users.

This method prevents users from having to remember
multiple passwords. It does issue other areas of security
concerns, namely that if a user walks away from there
computer while it is logged in, someone else could get
special access. This problem is evident in any system,
and should be addressed using business practices (ie,
locking workstations).


Chris Nebinger

 

[CPBV]

Thank you both, but for both suggestions: I don't
understand how to get it done. Could you clarify ?

 

[Jeff Boyce]

What you are asking for is more than I can provide via the newsgroups, given
my current commitments. I suspect an introductory course on Access would
provide some experience you could use to accomplish your goal.