Re: Programmatic Operator Verificaton

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Douglas J. Steele (NOSPAM_djsteele_at_NOSPAM_canada.com)
Date: 08/02/04 

Date: Mon, 2 Aug 2004 06:04:42 -0400

Randy Birch has a couple of things at his VBNet site that may be of use:

Authenticating a User though the NT Challenge Process
http://vbnet.mvps.org/code/network/acceptsecuritycontext.htm
Verifying a User Account using LookupAccountName
http://vbnet.mvps.org/code/network/lookupaccountname.htm

Obligatory warning: Randy's site is aimed at VB programmers. There are
significant differences between the Form object in VB and Access, so not all
of his examples will work in Access without some tweaking. I looked quickly
at these two samples, though, and I think you should be okay. 

-- 
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"Marco" <killspammjc@ams.co.za> wrote in message
news:OcBaQLGeEHA.3664@TK2MSFTNGP12.phx.gbl...
> Within my application I need to verify at certain stages (i.e. prior to
> sensitive operations) that the current operator is in fact the person who
is
> logged on to the operating system. Is there a way I can force the operator
> to reenter his/her password and then programmatically validate it.
>
> OR is there another way I can achieve the same goal.
>
> Any suggestions will be appreciated.
>
>