Dino, It can work if you keep track of the machine ID for the user logged in using the Win API. Then you use the machine ID as the unique instance of the user. That is the way I would do it. And, since you have total control over the install since it is an instance of the MSDE, they do not have any access other than through your program since they do not know the user ID and password for getting into the database.
Robert L. Stewart The Dyson Group International Software for the Non-profit Enterprise Expanding your Sphere of Knowledge Quoting Automatic digest processor <[EMAIL PROTECTED]>: > Date: Mon, 20 Mar 2006 16:23:21 +1200 > From: Dean Cleaver <[EMAIL PROTECTED]> > Subject: Re: Slightly OT - how to be sure I am getting data from a local db > > Robert, > > That won't work because the system can sometimes use multiple > connections, because of background threads etc. And I would personally > find the idea of logging when a user starts/stops the app unreliable > also, because if the power should fail then they won't be logged out, > and can never log in again. > > Also, there is still nothing to stop me listening to port 1434 and > redirecting that traffic to a server somewhere. > > Dino > > -----Original Message----- > From: Discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Robert L. > Stewart > Sent: Monday, 20 March 2006 16:14 > To: [email protected] > Subject: Re: [ADVANCED-DOTNET] Slightly OT - how to be sure I am getting > data from a local db > > Dino, > > The simplest way is to install the MSDE as an instance on the local > machine and not use the SA account for the login, create your own > there also. Use a connect string for that instance and redo it each > and everytime that the program is opened. > > Then add a table that keeps track of how many times the user is > logged in and limit the users to 1 instance. > > Robert > =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
