password input mask

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I just updated an Access 97 database to 2000 and the logon and the logons
quit working. This database was created by someone who has left and I am
trying to decipher the code. On the logon form they were using
recordset.clone to match the logons and passwords to a table. On the form
the text field is using the password input mask which makes the password
"****" so the password doesn't match the password in the table. I changed
the input mask to password in the table. When I do a watch on the script on
the form, the password on the form is "****" and it shows the password in the
table as true letters, not the "****" so they don't match and it creates an
error. When I put a text box on the form from the table it shows the
password as "****" like it should. I read it stores *** as the true
characters. So why don't they match and work?
 
This sounds like a "home-grown" security system. Which is in some ways
excellent, because no-one here can know off-the cuff how it works or what it
does :-)

The "usual" security system is Access User-Level-Security, which just about
anyone can break with sufficient general knowledge. User-Level-Security of
itself needs no code (though extensions can be written to it)

Can you confirm whether it has User-Level-Security or not? (eg what does the
logon screen look like?) If it's "home-grown" security, it's likely some code
didn't convert properly (determined through compiling it), or Something Else
<g>

Chris
 
Back
Top