>You don't need any special controls. See
http://www.craigberntson.com/Articles/kb003.htm>
Hey Craig,
I was hoping for a non table-based solution - obviously trying to be too clever. I did look on your site and have come up with an alternative solution.
The first solution (user ids) I agree won't work as you'd need to provide a reset solution.
The second solution, in my case, won't work as the database will, on some sites, be moving to a server and connecting via ODBC so won't necessarily have direct access and the server would not be able to work that way.
My solution is to use the machine name similar to the users table solution - this would overcome the reset problem as it will be based on the machine. If the PC crashes, next time they log in, it will find the machine name. Only when the number of machines passes the number allowed do you prevent access. Thinking while I'm typing, there could be a problem if a PC dies and they set up a new PC but then there could be an external app to clear the machines table down on the installation CD.
Lots to think about...