User Maintained Passwords

  • Thread starter Thread starter Allan
  • Start date Start date
A

Allan

Thanks to some help from this message baord, I have
successfully set up security on a database and am using
this information to limit the records a user can access.

I have one more hurdle to overcome - Is there a way to
force a user to create/change a password once
established. I plan on granting access to the database
through a shared drive. I have a list of users that will
be established. Each user would be able to log in using
their pre-defined user name. In order for security to
successfully work, however, a password needs to be
established. What methods would be used to force a user
to create a password - or change a password (in a
situation where a defalt password such as "welcome" is
previously established)?

Thanks,

Allan
 
Hi Allan,

You will have to build that into your application. Here's an article that
should help:

200665 ACC2000: How to Change User Passwords Programmatically Using DAO
http://support.microsoft.com/?id=200665

I hope this helps! If you have additional questions on this topic, please
respond back to this posting.


Regards,

Eric Butts
Microsoft Access Support
(e-mail address removed)
"Microsoft Security Announcement: Have you installed the patch for
Microsoft Security Bulletin MS03-026? If not Microsoft strongly advises
you to review the information at the following link regarding Microsoft
Security Bulletin MS03-026
<http://www.microsoft.com/security/security_bulletins/ms03-026.asp> and/or
to visit Windows Update at <http://windowsupdate.microsoft.com/> to install
the patch. Running the SCAN program from the Windows Update site will help
to insure you are current with all security patches, not just MS03-026."

This posting is provided "AS IS" with no warranties, and confers no rights


--------------------
| Content-Class: urn:content-classes:message
| From: "Allan" <[email protected]>
| Sender: "Allan" <[email protected]>
| Subject: User Maintained Passwords
| Date: Wed, 7 Apr 2004 08:18:15 -0700
| Lines: 19
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcQcs4xSFQwNoM/pTNyzCgJ2l//3KQ==
| Newsgroups: microsoft.public.access.security
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.access.security:9769
| NNTP-Posting-Host: tk2msftngxa12.phx.gbl 10.40.1.164
| X-Tomcat-NG: microsoft.public.access.security
|
| Thanks to some help from this message baord, I have
| successfully set up security on a database and am using
| this information to limit the records a user can access.
|
| I have one more hurdle to overcome - Is there a way to
| force a user to create/change a password once
| established. I plan on granting access to the database
| through a shared drive. I have a list of users that will
| be established. Each user would be able to log in using
| their pre-defined user name. In order for security to
| successfully work, however, a password needs to be
| established. What methods would be used to force a user
| to create a password - or change a password (in a
| situation where a defalt password such as "welcome" is
| previously established)?
|
| Thanks,
|
| Allan
|
 
I can't see the original post, so let me jump on to Eric's reply.

The article will doubtless help you write code to let the current user
change his password. But I think your requirement is to >force< the user to
change his password, if he has logged-on using a predefined password such as
"guest", his username, or whatever, that you have set up for him initially.

If so, here's what to do. In your database startup form or code, try to
create a temoporary workspace using the current user's name, and the
appropriate predefined password ("guest", his username, or whatever):

dim ws as workspace
on error resume next
set ws = dbengine.createworkspace ("temp", CurrentUser(), "guest")
if err.number = 0
' it worked!
endif
on error goto 0
set ws = nothing

If it >works<, you know that he >has not< changed his default password. Then
you could redirect him to a suitable screen to change his password. Then
repeat the check above, to make sure that he did not just re-enter the
default password!

If the code above gets an error (signified by err.number >not< equal zero),
you know that he has changed his password.

HTH,
TC
 
Back
Top