1) The VS tools used to work fine before I upgraded to
Win XP.
2) They also work fine on 2003 Server platform.
3) Also, the ODBC administration tool is unable to find
the SQL instance.

I don't believe it's a VStudio or VS.Net problem.

Thanks anyway.

>-----Original Message-----
>Hi Larry,
>
>It seems that you want Query Builder in VStudio 6 and
VB.Net to enumerate
>SQL Server instances on the network. Am I right? If so,
it seems that the
>problem is the functionality of these specific tools and
I would suggest
>that you check with newsgroups specific to these tools,
e.g.
>microsoft.public.vsnet.ide.
>
>
>Bill Cheng
>Microsoft Online Partner Support
>
>Get Secure! - www.microsoft.com/security
>This posting is provided "as is" with no warranties and
confers no rights.
>--------------------
>| Content-Class: urn:content-classes:message
>| From: "Larry Stall" <lstall@gilmanassembly.com>
>| Sender: "Larry Stall" <lstall@gilmanassembly.com>
>| Subject: MSSQL2K ODBC in WinXP Pro
>| Date: Tue, 5 Aug 2003 07:42:05 -0700
>| Lines: 20
>| Message-ID: <0dd501c35b5f$bd8c38d0$a301280a@phx.gbl>
>| MIME-Version: 1.0
>| Content-Type: text/plain;
>| charset="iso-8859-1"
>| Content-Transfer-Encoding: 7bit
>| X-Newsreader: Microsoft CDO for Windows 2000
>| X-MimeOLE: Produced By Microsoft MimeOLE
V5.50.4910.0300
>| Thread-Index: AcNbX72JlEoeybbQSVu/wDnRHzxzZg==
>| Newsgroups: microsoft.public.sqlserver.odbc
>| Path: cpmsftngxa06.phx.gbl
>| Xref: cpmsftngxa06.phx.gbl
microsoft.public.sqlserver.odbc:39377
>| NNTP-Posting-Host: TK2MSFTNGXA11 10.40.1.163
>| X-Tomcat-NG: microsoft.public.sqlserver.odbc
>|
>| Recently upgraded a development station from Win2K Pro
to
>| WinXP Pro. It has a MSSQL2K Personal Edition running
so
>| it can be used for development when not connected to
the
>| company domain (with MSSQL2K servers). It is used for
>| VStudio 6.0 and VStudio.Net development.
>|
>| Recently, while not connected to the network, I found
>| that when I tried to make a new DSN in ODBC for SQL
>| Server, NO servers were enumerated, not
even "(local)".
>| If I force "(local)" as the server, the connection is
>| established. However, if I use Query Builder in
VStudio
>| 6, unless I use the prevously created DSN, no servers
are
>| enumerated. The worst part is using VB.Net, I get
OLEDB
>| data objects instead of SQL. I tried re-installing
>| VStudio.Net, .Net Framework, and MSSQL2K and SP3, but
no
>| change.
>|
>| When I'm off the domain, the log-in switched to "Fast
>| User Switching" mode. COuld this be the source of the
>| problem??
>|
>
>.
>