Wortz, Charles
CWortz at tea.state.tx.us
Mon Aug 18 13:20:36 CDT 2003
Greg, Once in a lifetime? Or once in a day? Or once in an hour? If it is the first, then you have a separate table with flags you set for each user. Once the flag is set, they are locked out forever. For the latter options, you add a date/time field to record when they accessed and then compare the time of their next attempt to access to see if the proper length of time has expired. Charles Wortz Software Development Division Texas Education Agency 1701 N. Congress Ave Austin, TX 78701-1494 512-463-9493 CWortz at tea.state.tx.us -----Original Message----- From: Greg S [mailto:weeden1949 at hotmail.com] Sent: Monday 2003 Aug 18 10:53 To: Access Developers discussion and problem solving Subject: [AccessD] Restrict # of User Logins to Access Hello everyone! I got a request from a client that I'm not sure how to handle...and I hedged enough so as NOT to commit to anything until I have it figured out. Their current system is in Access 97, using full Access's security. It's setup fairly well, with users being members of groups and rights assigned to the groups. Now she's thrown me a curve. She wants to allow users from another department to login to her system, but ONLY ONCE (her reasoning is sound - she does not want users from another group tying up all her resouces and licenses with multiple logins). That is, that username can only login to the Application once...one concurrent usage. Windows security would do this easily, but Access 97's doesn't have a place to select the number of logins per user. Any suggestions on how to do this? I've just had a second temporary crown put in this morning (since last week), it's fairly early, I've NOT had sufficient coffee, and I'm a bit fuzzy (fuzzier??) around the edges this morning and it's not readily apparent to me on how to do this. Thanks!! Greg Smith weeden1949 at hotmail.com