Stand alone 2000 clobbers 7.0 remote

[rgordley]

As a developer, on my workstation I have to have various applications corresponding to what I may have to support for clients. Currently I have SQL 2000 running on my desktop and SQL 7.0 running on the network server. Previously I had SQL 7.0 running stand alone on my desktop as well as the network server and had no problems. Now I have to have the enterprise manager running and connected to the network SQL 7.0 in order for my applications to connect to it. Previously I could connect to the network server directly from an application without the Enterprise Manager running. In addition, everytime I start the EM, I have to delete and re-register the network server before the EM can connect. Needless to say this is a huge pain. Anyone have any ideas?

 

[rgordley]

Moving this up in hopes of an answer

 

[tlbroadbent]

Could you have a conflict between the name, address or alias of the server running on the network and the one running on your desktop?

Check the server aliases and libraries using the the SQL Server Client Network Utility.

Can you connect to each SQL Server using Query Analyzer? Or do you need to run EM in order to connect to the network server with QA? Terry

http://members.home.net/tlbroadbent/index.htm

 

[rgordley]

Terry,

I checked the aliases and libraries and everything is as it should be. Oddly, though my VB apps can connect to the network server when EM is running, Query Analyzer cannot. The error message is "ODBC Msg 0, Level 16, State 1"