Max Wanadoo
max.wanadoo at gmail.com
Sun Jan 6 12:01:18 CST 2008
Yes, my user numbers was part of the Licence Key which also gave Expiry Date plus other stuff (ie, only a given number of users could install the FE before it refused to install any more). When Expiry Date approached it gave warnings and then if not renewed only gave users READ only access to data. Can be as flexible as you wish, all with custom properties on the BE Max -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin at Beach Access Software Sent: Sunday, January 06, 2008 5:54 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Number of Users Max: Looks like a good approach. Avoids the Access workgroup and security thingies. Always a plus. The max users I can embed in the product key. Thanks. Rocky -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo Sent: Sunday, January 06, 2008 9:09 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Number of Users Rocky: Some years ago, I had to do this. There may be better ways, but what I done then was. 1. Set up TWO custom property on the BE (say, MaxUSersAllowed, UsersLoggedOn). 2. Set the MaxUsersAllowed to the appropriate value. 3. Each time a FE opened, it checked the UsersLoggedOn against the MaxUsersAllowed and if it was at the max value, it gave a message and closed down the FE else it increments this value. 4. Each time a FE closes, it decrements this UsersLoggedOn value. If at zero, it left it alone.( see below). You will need a mechanism to clear down the UsersLoggedOn value as it sometimes happens that people "bomb out" of the FE and the UsersLoggedOn value is not decremented properly. I therefore had a separate mde (compiled so no user can access the code with password access for the SyAdmin) which when run, resets the UsersLoggedOn value to 0 and close the BE (thus dropping all connections). With suitable messages/warning first of course. (ie, Get everybody out of the system 'cos it is shutting down, etc) HTH Max -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin at Beach Access Software Sent: Sunday, January 06, 2008 4:19 PM To: 'Access Developers discussion and problem solving' Subject: [AccessD] Number of Users Dear List: What is the easiest way to restrict the number of users in a FE/BE application? MTIA Rocky -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.17.13/1210 - Release Date: 1/5/2008 11:46 AM -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com