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

At 11:00 PM 3/17/2006, you wrote:
>Date:    Fri, 17 Mar 2006 19:25:18 +1300
>From:    Dean Cleaver <[EMAIL PROTECTED]>
>Subject: Slightly OT - how to be sure I am getting data from a local db
>
>Hi,
>
>I've got a project that I am considering making free for single users,
>whereas the networked version would be licenced. So, each installation
>would have MSDE installed on the local machine and the free version
>would only connect to local host.
>
>However, it's easy enough to use a port redirector on port 1433 to
>defeat this, and redirect it to another server/machine. So I can't rely
>on using 127.0.0.1 or (local) to connect to SQL Server.
>
>I could try query SQL Server for @@SERVERNAME and compare that to the
>local machine name, but that's the name of the machine SQL was
installed
>on, not necessarily the same as the name of the server now, so this
>could be unreliable if they change machine names - unlikely I guess,
but
>possible.
>
>Any other ways I could try to guarantee that the SQL Server is actually
>on the local machine?
>
>Dino

===================================
This list is hosted by DevelopMentor(r)  http://www.develop.com

View archives and manage your subscription(s) at
http://discuss.develop.com

===================================
This list is hosted by DevelopMentorĀ®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com

Reply via email to