Run-time, App-specific license checking?

[servoss]

I searched through the fora here to no avail.

I have a database that I want to distribute. When distrbuting the database to a site, I want to be able to ensure that only a specific number of users access the database simultaneously. Or, that specific users, or specific computers access the networked file.

This would be a similar situation as an application with 10 licenses checking to make sure that no more than 10 users execute the app simultaneously.

Is there a straightforward way of doing this? Is there a way to do this regardless of OS and networking (or no networking)?

Whatever your thoughts, they are appreciated.

Tom

 

[John.Woody]

Tom

If everyone logs on and off the db you can create a table of people who have logged on and not logged off. A Yes/No Field will suffice, however you could store the userID, computer name, user name for the pc, log on time and log off time. When someone logs on to the db you could count the number of ticks, and let them in, or kick them out accordingly.

 

[mark curtis]

if u develop the db as a runtime with Office developer then distribute as a runtime there are no licencing issues as the developer edition covers this.

 

[servoss]

I'm affraid I missed the mark...

Thank you for the information, but I actually WANT to control the number of concurrent users. Furthermore, I will not know anything about the LAN upon which the database is used. In fact, it may not be used on a LAN at at - it might be a single user/computer, in which case I want little if any control other than to prevent copying/distribution. As for the distribution, I'd very much enjoy the ability to provide a reg number that must be entered for use AND the reg would only work for a specific site - that redistribution would be precluded.

I hope this clarifies the issue - sorry fo rthe confusion and thanks, again, for your thoughts.

Tom

 

[servoss]

Since I didn't get a reply...

I went ahead and coded something up myself. In a nutshell, I created a tabel of login date and time and logout date and time. Then, when someone logs in, I look for records of people logging in without being logged out. If there are too many, I give an error message. If there are not too many I create a new record for the new log on.

When logging out, I search for the same username and record the logout date and time. pretty simple.

Thanks for the help, I guess.