Re: moving EXE from MSDE PC to SQL Server PC

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi Andrea,

Yes, at my place, I do not have a domain and I don't have any network
problems.  Plus I can have my wife's PC use the EXE if I code it like
"server=RICK;trusted_connection=true;database=Pubs", everything is fine.

I assume you are not under a domain, but just a p2p lan... and I assume no network problems are present on the WinXPsp2 boxes as you already fixed firewall troubles... 

If re-coded the application for my client (his server's name is SERVER)
so the code now reads

"server=SERVER;trusted_connection=true;database=Pubs"

it works at his site.

I also used the VB debugger to find out the problem, the "catch" part
never gets triggered.  Even if I make up a string like

Try
   sqlConn = New SqlConnection("server=NoSuchName;  ....
Catch ex As Exception			' It never gets here?!
   MsgBox(Err.Number, , Err.Description)
   sqlConn = New qlConnection("server=SERVER;  ...
End Try

Thanks for your great description about trusted connections.  I did
create identical profiles (name and passwords, both admins) on both PCs
in my peer LAN.

I only have MSDE on ONE PC, mine. I thought that since my wife's PC can
access my MSDE (if I code it "server=RICK..." connection), then she doesn't need MSDE.

more, you have to grant YourWifePC\Rick account login permission to YourWifePC MSDE instance... (or make YourWifePC\Rick account member of a WinNT group with login privileges)..

You are right, my customer has SBS 2000 which includes SQL 2000.
I tried connection strings of: "(local)", and "localhost" but the only one that works is if I use "server=SERVER"

It isn't that big of a problem as I change one line of code, hit F5 to recompile the new EXE and upload the file to my client. Then I change it back and work on my PC.

I just don't understand why it won't work with any other connection string, but at least it works :)

I also have it working on their server with regular (not admin) accounts :)

on your customer's server, assuming he has a DC and not a workgroup, it should run fine without additional mapping needs, as long as the used WinNT account has individual login privileges or is member of a login granted WinNT group (and please do no use Administrators overall :D)
so, depending on you app and on your customer needs and HD/SW requirements, perhaps a standard SQL Server authenticated connections scenario could be better.. even if trusted connections is preferred .... 

Thanks for all your help!

Richard

p.s. Now that SBS 2003 SP1 is out, I will install it on one of my PCs :)
.

Quantcast