Windows 7 Windows 7 and SQL Server 2000

[OrbikDevelopment]

Hello,

I am moving an Access 2007 project to Visual Studio 2013 Net which means I am having to use Windows 7 where currently the clients are on XP.

Everything seems to be ok except for one strange issue. For some reason Windows 7 will not create an ODBC connection to SQL Server 2000 (which is running on a 32 bit Windows 2003 server). it keeps saying "the server does not exist or access denied"???

XP computer connect using the same ODBC connection settings with no issues.

Have tried setting access to ports "1433" and "1434" in the firewall and even turning it off still no connection, the Windows 7 computer can see and ping the 2003 server and vice versa, so I am confused as to why Windows 7 can't connect when XP can.

Is there something simple I am missing such as Windows 7 is not compatible with SQL server 2000??

The Windows 2003 server has active directory and DNS on it (the Windows 7 client seemed to need a DNS address to connect to the server).

All computers are 32 bit.

 

[Neemobeer]

You should be able to connect to it with IP/port or \\servername\instancename if you can't connect to it with the latter then either the sql server browser service isn't running or you might have a DNS issue. Can you ping the server by DNS name? Also do you have the SQLNCli driver installed?

 

[BIGBEARJEDI]

I believe your guess is right based on my experiences from 15 years ago using MS Server 2000 and SQL Server 2000. Newer workstation clients such as Win7 are not compatible with any version of SQL server 2000; that stuff is seriously dated, and I know for a fact that SQL server 2000 app is not compatible on anything newer than Server 2000 without upgrading the SQL server app itself.

For example, to run SQL server on MS Server 2003, you have to upgrade to SQL server 2003, MS Server 2008RT, you have to upgrade to SQL server 2008, etc. This is or at least used to be a Microsoft licensing issue. You're taking the tack of trying to solve this by applying network parameter tweaking, and that's not going to work. It's not an address, DNS, DHCP, proxy, firewall, or protocols issue. The app itself is being blocked by both a compatibility and a licensing problem. Win7 clients were developed in 2009 which is 9 years after SQL server 2000; an eternity in programming and OS terms. That's nearly a decade of technology advances you are trying to leapfrog with a modern windows client. Windows clients designed to work on SQL server 2000 were Win98, Win2k, and early XP beta. I'm almost certain that's not going to work. I won't go into boring tech details here; but this is the long and short of it. I'd suggest you have your Client or Company upgrade their SQL server to at least the 2003 version if not the 2008 version. As far as licensing goes, if you must have the 2008 SQL server running on a MS server 2008RT, you'll be looking at upgrading and or building a completely new core network server such as server 2008RT in order to host the SQL 2008 app on. Flat-file databases such as the Access 2007 you mentioned will work on 2008RT server without having to have the corresponding SQL server version (SQL server 2008 app) however. In fact last year on my 2008RT server, I was able to run my Access2003 database on Access2007 installed on Vista & Win7 clients connected to the 2008RT server as they don't require the SQL server app module to be installed and running on the server itself. I have no idea what server version something like Visual Studio2013 requires; you can call Microsoft and ask or a major Microsoft platinum software reseller support such as CDW or PC Mall.

Hope that helps.
<<<BIGBEARJEDI>>>

 

[Neemobeer]

Windows 7, provided the user has the SQL native connection driver, should have no problems connecting to a SQL 2000 database. May need the 2005 or 2008 connection driver though.

 

[BIGBEARJEDI]

@Neemo: Really? Didn't know that a connection driver would handle that. What about syncing-delays through the conduit, undue bandwidth usage on the W7 client connection? <<<BBJ>>>

 

[Neemobeer]

Yup, you need to install a driver to communicate to a SQL server. Download Microsoft® ODBC Driver 11 for SQL Server® - Windows from Official Microsoft Download Center SQL is transaction based and it can handle data very quick so it's pretty difficult to overload a SQL server or cluster depending on the SQL configuration.