
Migration to VS 2003 worked though I don't know why
I made the migration to VS 2003 from 2002 and it seems to have worked though
I can't explain some things. I am perplexed because of the difference in
the way I used to access my SQL Server 2000 database and the way I do now.
Prior to the move the database I am interested in resided in a Server Name
of P3800\NetSdk. (My machine name is P3800). Now I am able to access the
same database but it is residing in a Server Name of P3800. Don't ask me
how I go it there but I did.
There are obviously some fundamentals that I do not understand wrt VS and
server group names. In the end it doesn't make any difference to me as long
as VS considers what I have done as orthodox and it works. Somehow, in the
past, I got it in my mind that there was some disadvantage or there was
something wrong in having a database in my local server. Is this OK? Does
it have to be or should it be in something else like NetSDK? Am I in Okey
Dokey land by accessing my database in Local?
I should add, however, that I must have something wrong because when I go
into a particular project, the computer halts for a long time and finally
comes up with a connection dialog that makes reference to the old
P3800\NetSDK. This is strange because no such directory even exists any
more. There used to be a dir under my Microsoft SQL Server directory called
$NetSDK but it is history now. How can I set things up so VS is happy with
it and it works too?