Solved

ADO Recordset Delete Error SQL 2005 DB

Posted on 2008-10-12
5
835 Views
Last Modified: 2013-11-16
Hi,

Any help on the following would be appreciated:

We have a VB6 application which uses ADO (MDAC 2.7) to connect to a SQL database. Recently we have been testing it using a SQL 2005 database and have come across a problem.

It would seem that if you try and issue a delete on a server side recordset you get the following error:

[Microsoft][ODBC SQL Server Driver][SQL Server]Could not find server 'WINXP-TEST-V\SQLEXPRESS' in sys.servers. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers.

If you change the recordset to client side it works fine. Unfortunately changing the recordsets to client side is not really an option as it is a huge program and to change all the cursors would be a massive task. An example of the code which creates this problem is shown below.

Has anyone got an idea why this does not work with a server side recordset?

Many Thanks
Dim cConnstr As String

    Dim oConn As New ADODB.Connection

    Dim rs As New ADODB.Recordset

    Dim cSql As String

    

    cConnstr = "Driver=SQL Server;Server=WINXP-TEST-V\SQLEXPRESS;UID=sa;PWD=sa1234;database=aa_jobdata"

    Set oConn = New ADODB.Connection

    With oConn

        .CursorLocation = adUseServer

        .Mode = adModeShareDenyNone

        .Open cConnstr

    End With

    

    cSql = "Select * From Costtype WHere Code = 'ZZZZ'"

    

    With rs

        .CursorLocation = adUseServer

        

        .Open cSql, oConn, adOpenKeyset, adLockOptimistic, adCmdText

        

        .Delete

        

        .Close

    End With

Open in new window

0
Comment
Question by:StevebData
  • 2
  • 2
5 Comments
 
LVL 142

Expert Comment

by:Guy Hengel [angelIII / a3]
Comment Utility
actually, deleting rows with recordset is not recommended at all...

it should rather be done like this:
oConn.Execute "delete From Costtype WHere Code = 'ZZZZ' "

Open in new window

0
 
LVL 75

Expert Comment

by:Anthony Perkins
Comment Utility
I will go out on a limb and state that you are not getting the error in the Delete method, but rather in the Open method.

But I agree with angelIII you should not be using a recordset in the first place.
0
 

Author Comment

by:StevebData
Comment Utility
The open method works fine, its just the delete which fails.

I know its not the most elegant solution or best practice but its what I inherited, and to change it would be a massive task as our code base is huge.

I should have pointed out that this application (which is about 10 years) old has been running on SQL 2000 for a number of years without any problems and its only when we tested it on a SQL 2005 database that we got these problems.

If anyone could explain why this method no longer works that would be a great help and would allow me to make an informed decision on what I do next.
0
 
LVL 142

Expert Comment

by:Guy Hengel [angelIII / a3]
Comment Utility
this is a named instance, which needs, for being connected with ODBC, to be aliased in the client computer's sql network utility...
or use another connection string, using the sql oledb provider instead, for example.
0
 

Accepted Solution

by:
StevebData earned 0 total points
Comment Utility
In case anyone gets the problem above, please see the following link:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=329107&SiteID=1

It was caused because the computer which the SQL server resides on had been renamed in the past.
0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Join & Write a Comment

Using SQL Scripts we can save all the SQL queries as files that we use very frequently on our database later point of time. This is one of the feature present under SQL Workshop in Oracle Application Express.
Never store passwords in plain text or just their hash: it seems a no-brainier, but there are still plenty of people doing that. I present the why and how on this subject, offering my own real life solution that you can implement right away, bringin…
As developers, we are not limited to the functions provided by the VBA language. In addition, we can call the functions that are part of the Windows operating system. These functions are part of the Windows API (Application Programming Interface). U…
Get people started with the utilization of class modules. Class modules can be a powerful tool in Microsoft Access. They allow you to create self-contained objects that encapsulate functionality. They can easily hide the complexity of a process from…

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now