dates not masked in table

[revlisj]

Hi, I applied a "password" input mask to a date field in a table, but the date value remains visible. The password mask works fine for text fields. Text values display as ***** when viewed in datasheet mode. Dates, on the other hand, display as asterisks as you are typing in a value, but as soon as you leave the field, the value displays, as if unmasked.

Cheers

 

[MarkK]

Make sure the InputMask property of the textbox that displays the date is also set to Password.
hth
Mark

 

[revlisj]

Thanks MarkK, but there is no text box displaying the date. I'm referring to the table datasheet view, not a form view. While entering a "password" masked date in the table, not a form, the asterisks appear as you type. But, as soon as you leave field, the date appears, unmasked. The same date field also shows up unmasked in a query built over said table.

 

[revlisj]

Thanks Pat,

I'm not attempting to enter data directly into tables, just testing some scenarios. This all comes down to data security/protection. I have a number of tables with masked fields (sensitive data). I'm attempting to prevent users from opening a table in datasheet view (via navigation pane, F11) and seeing data they should not be seeing. Text fields see to work fine, date fields, not so much. I'm using forms and reports to unmask the masked table fields. This seems to be a hole in Access security.

Cheers

 

[jumbotrano]

Masking isn't going to solve this problem. If your data is that sensitive, you should probably look at something other than Access as your FE. Even if you distribute an .accde, the users can still view the tables and then the data they contain. You can hide the tables and that makes it harder for the average user to locate. You can also set the database properties to prevent the use of the shift-bypass so the user won't be able to circumvent your opening form. But, if you have a competent hacker, nothing in Access is secure.

True, with the right skills, access is kind of vulnerable