"Rick Brandt" wrote:

> Mrs. Chart Problem wrote:
> > Any ideas?
> >
> > I have implemented user-level security and my application has to
> > conform to 3 password guidelines.  Minimum of 6 characters, change
> > evey 35 days, and maximum of 6 unauthorized login attempts.  I built
> > a form that is attached to a table with last password change date
> > information and that form limits password length so the first two are
> > relatively easy. I am pretty stumped on the third.  Anybody know if I
> > can even access (no pun intended) this type of information?
> >
> > Thanks!!
>
> As far as I know you could only do this if you first launched a non-secure
> app whose only purpose is to prompt for the user name and password that will
> be used to open the secure one.  The non-secure app could attempt to open a
> workspace using the appropriate MDW file and user credentials and could
> allow "n" attempts before shutting down.  When successful it would then use
> those credentials to launch the secure app and then close itself.
>
> You can't do this actually IN the secure app because no code to give you
> that logic can be run until you are already in.
>
>
> --
> Rick Brandt, Microsoft Access MVP
> Email (as appropriate) to...
> RBrandt   at   Hunter   dot   com
>
>
>