I have set up a users file to compliment my dbs so that I can control access and have the user's name in a global field for electronic signatures. I have a script that date/time stamps and adds the user's name per his/her login. Works great, however, our QA dept. wants the script to also prompt the user to re-enter his/her password for added security (in case s/he walks away from the desk without logging out, I guess). My files are served and my users are on thin clients so "Current User" doesn't work. Any suggestions? Thanks.

Version: v5.x

Platform: Windows XP

If you are using FM server, there is a setting that will have FM server automatically disconnect any user after predetermined period of inactivity.

Thanks- I thought of that but the FDA (I'm in the dreaded medical field) doesn't think that is good enough to prevent someone from falsifying an electronic sig. And, my users whine if I make it a very short period. I need to "guarantee" that the e-sig is actually who it is supposed to be and re-entering a password seems the best route.

You could have the time stamp script save the time/date in a global variable every time it runs. Then it could compare the current time/date to the time/date when it was last run. If it's more than X minutes, then it could display a message that the user must login again, and then it would Close the file. User would then have to re-open and enter password.

You could probably make the operation neater using some auxiliary opener files to perform this. But, you have to be careful that the opener files won't re-open the main file without having to enter the password.

In case anybody is wondering, I figured out how to do this in a way that is easy for the user. Since I have a "user" file and everyone logs in with a name and password, I put a password field on the layout that is compared to the user's global password used to log in. If the user submitting the record knows the password of the user initiating it (i.e.- it is the same user), then it is a match and the record is submitted. If not, the user is stuck in a loop until s/he chooses to exit the application (or gets the right password). To keep this short, if anybody wants the details on how to do this, I am happy to share them. Email me: [email protected].