Nope. Major PITA. In most retail stores where there is that kind of system, I see the current user log out when they step away. The app is not totally shut down, it just goes back to a login form.

I do the same thing where in my File/Exit menu option, I log out the user and present the login form again. This form has the option of quitting the app. If the user clicks the close button, the app shuts down completely.

I would be quite annoyed if I had to enter a password every time I opened an invoicing form or any other form.

>Hi Mark,
>
>The only problem is that my application is used in a retail environment where multiple users can be using the same workstation. With this in mind do you think it is ok to ask for passwords at the form level?
>
>Thanks for you opinions,
>Paul acton
>>>I was wondering if anyone could shed some light on how they use passwords for menus.
>>>
>>>I was thinking about having a file with each form's name in it and a password level.
>>>
>>>Then the doform method of my form manager class could ask for a password and then compare the level of that password to the level in this new table for this particular form.
>>>
>>>Does this make sense? Any other ideas?
>>
>>I do not like the idea of a password entered for each form. Have the user enter an ID and password when they launch your app. Store their ID and or access level to an oApp object property for future reference.
>>
>>I have a UserProfile table that has a record for each function a user can potentially do. [UserID [I], Descript [C], ParmName [C], Granted [L], ChkSum [I]]
>>
>>The ChkSum field is a calculation based on the sum of the check sums of the data values in the first 3 fields plus some arbitrary geometric number of the field number [i]. When a user logs in, I create an oApp array property that holds the ParmName [parameter name] and Granted fields for each record for that user in the ProfileTable. If the ChkSum does not match [e.g., user hacked the table], the access for that parameter is set to false.
>>
>>Then, at the form or field [textbox] level, I can call an oApp method which returns .T. or .F. based on the value of Granted:
>>
>>llRetVal = oApp.GetUserParm(ParameterName)
>>
>>This user profile lets me restrict access to forms, reports, tables and even down to the field level.