RE: hoping this is easy - passwords
From: 111 (spam_at_spam.com)
Date: 06/21/04
- Next message: John Vinson: "Re: Form will not stay open"
- Previous message: Praveen Manne: "Re: How to get the value in previous record to current record?"
- In reply to: Mingqing Cheng [MSFT]: "RE: hoping this is easy - passwords"
- Next in thread: Mingqing Cheng [MSFT]: "RE: hoping this is easy - passwords"
- Reply: Mingqing Cheng [MSFT]: "RE: hoping this is easy - passwords"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 21 Jun 2004 21:03:21 GMT
Hi, thanks for the feedback. actually i'm not too interested security as i am
reports being automatically created with the correct user information. SOme of
these reports are fax coverpages etc which, once the user logged in correctly,
would put his name , email address and phone ext. in the correct place on the
coverpage.
Do you have a simple way of doing this?
tks
In article <Tww0bO3VEHA.4088@cpmsftngxa10.phx.gbl>,
v-mingqc@online.microsoft.com says...
>
>Hi Steve,
>
>>From your descriptions, I understood that you would like to specify user
>according to their user name and correct password. Have I understood you?
>If there is anything I misunderstood, please feel free to let me know:0
>
>Based on my knowledge, unfortunately, there is no easy way to do it.
>
>First of all, Access have it's own security mechanism called workgroup
>information files (mdw). With the help of mdw files, you could make your
>mdb file user input their user name and password once they are trying to
>open the file. Without correct user name or password, they could not even
>open the mdb file.
>
>If you have logged in as user1, you could use CurrentUser Method in VBA to
>get to know current user of your access file is 'user1'
>
>More information about mdw files and how to set this kind of security could
>be found at
>
>Understanding the role of workgroup information files in Access security
>http://support.microsoft.com/default.aspx?scid=kb;en-us;305542
>
>Overview of how to help protect a Microsoft Access Database
>http://support.microsoft.com/default.aspx?scid=kb;EN-US;289885
>
>Secondly, you may make your own security mechanism. Admittedly, it's rather
>complex to do so. You will have to make a table to resotre the user
>information(including password and anything else you like) and then use
>your own security arithmetic to restore password preventing it is known by
>others. Force the user check by means of Load_Form()
>
>In all, I don't think your requirement could be fully realized with ease.
>It's risky to make your own security mechanism as it's too easy to be
>attacked.
>
>Hope it helps and if you have any questions or concerns, please feel free
>to let me know:)
>
>
>Sincerely yours,
>
>Mingqing Cheng
>Microsoft Developer Community Support
>---------------------------------------------------------------
>Introduction to Yukon! - http://www.microsoft.com/sql/yukon
>This posting is provided "as is" with no warranties and confers no rights.
>Please reply to newsgroups only, many thanks!
>
>
>
>
- Next message: John Vinson: "Re: Form will not stay open"
- Previous message: Praveen Manne: "Re: How to get the value in previous record to current record?"
- In reply to: Mingqing Cheng [MSFT]: "RE: hoping this is easy - passwords"
- Next in thread: Mingqing Cheng [MSFT]: "RE: hoping this is easy - passwords"
- Reply: Mingqing Cheng [MSFT]: "RE: hoping this is easy - passwords"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|