Client app doesn't work now!

microsoft.public.sqlserver.programming

27 Oct 2006 5:39 PM

Rockitman

First a little history:

We have a Pentium II server running SQL 7.0. The SQL has a database that
our users connect to using a client front end app that was created by a
former programmer in our office. The file server name in the beginning was
called FRE3.
In the beginning the server was running NT4 and the users were on Win95
desktops.
We had a migration a few years ago where the server was upgraded to Windows
2000 server and the desktops were upgraded to Windows 2000 Professional. We
also had to make a server name change to fall in line with official naming
conventions. The server's name was changed to NTFRE. It was and still is
just a member server in our AD.
Of course, the client app had to be modified as it refers to the server name
and us non-programmers figured out how to change the name in the Visual Basic
code and recompiled a new executable and it worked fine. Just had to change
one instance in the code where it names the server.

We are now going through a new migration. We have a new box and have
installed Windows Server 2003 Enterprise on it. We have also installed SQL
2000 on it. Have updated all service packs and everything. Ran the copy
database wizard and successfully brought over the database from the SQL 7.0
server, as well as user logins. User destops are being migrated to Windows
XP as well.

So we broke into the code again, and changed the server name again like last
time, (new 2003 server is called S2K3-FRE-SQL1), and recompiled a new
executable.

Houston, we now have a problem. When I executed new executable on new XP
machine, I get this error message after logging in:

Run Time Error - '2147217900(80040e14)
Incorrect syntax near keyword 'function'

I also get the same error running executable on a current Windows 2000
platform.

Does this error message mean anything to any of you gurus?

There is one bit of info that I need to relay, not sure if it matters or not:

The old server running 7.0, in Enterprise Manager, under SQL Server Group,
it states 2KFRE (Windows NT).

In the new server running 2000, in Enterprise Manager, under SQL Server
Group, it does not state the name of the server (S2K3-FRE-SQL1), it just
states Local (Windows NT).

Should I worry about this? Is the code looking for S2K3-FRE-SQL1 and seeing
the word Local instead, thus giving me my error message?????

Do you believe that the client code needs to be modified somewhere else now??

Is this error message a reflection of code built to address a SQL 7.0
installation and now it doesn't work as it's trying to talk to a SQL 2000
installation??