March 18, 2002 at 9:24 am
I have an application with an Access 2000 user interface where the user has the option of using Access Jet Engine as back-end database or SQL Server. With SQL Server though, I've kept 1 table in Access 2000 because I don't know how to handle the Access "Password" input mask for 1 of the fields in SQL server. Any ideas?
Thanks.
March 18, 2002 at 9:52 am
I don't do much Access development but a mask can be easily implemented via code in the keydown or keypress event of a control. Doesn't matter where the data is stored, it's just how you format it.
Andy
March 18, 2002 at 10:01 am
That's fine for forms control, but the Access input mask is applied on the table field itself in design mode. Like in Access, I want to prevent users from seeing the value of this password field even if they open the table directly or via sql select query. In Access you will see **** when you attempt to query such fields no matter how you do it.
March 18, 2002 at 11:21 am
You could use a view that returned asterisks, but then you couldnt query on it! How many of your users need access to this info? If you handle setting the password via stored procedure and have another for login validation would you need to query the table directly? The biggest problem I see with keeping it in Access is that you're getting it backed up as part of the db..along maybe with issues of how to make sure everyone has the current table.
Andy
March 20, 2002 at 2:42 pm
Yes, I would need to query/manipulate the table directly, so the view solution would not work. I wonder if there's some way to mimick Access' handling of the password input mask via a user-defined data type.
I would prefer to have the table in SQL server, too, but since the front-end has a link to the proper db back-end, there's no issue with making sure everyone has the current table.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply