FIX: You receive an "Unspecified error" error message when you use the OLE DB Provider for SQL Server to modify a table row

Steps to reproduce the problem

To reproduce the problem, create an update trigger that uses the FETCH command, and then create a Microsoft Visual Basic 6.0 project:

1. Start SQL Query Analyzer, and then connect to an instance of SQL Server 2000.

2. On the Query menu, click Change Database. The Select Database of Server name dialog box appears.
   
   Note Server name is a placeholder for the name of the instance of SQL Server 2000 that you are connected to.

3. In the Name column, click pubs, and then click OK.

4. In SQL Query Analyzer, run the following Transact-SQL statement:

   CREATE TRIGGER jobs_Trigger1
   ON dbo.jobs
   FOR UPDATE AS
   
   BEGIN
   
   DECLARE    @job_id int
   DECLARE job_inserted_cursor CURSOR
   LOCAL
   FAST_FORWARD
   FOR 
     Select job_id 
      FROM inserted 
   
   OPEN job_inserted_cursor
   
   FETCH NEXT FROM job_inserted_cursor    /*  The error occurs. */
   /* FETCH NEXT FROM job_inserted_cursor INTO @job_id        The error does not occur. */
   
   CLOSE job_inserted_cursor
   DEALLOCATE job_inserted_cursor
   
   END
   

5. Start Microsoft Visual Basic 6.0.

6. In the New Project dialog box, click Standard EXE, and then click Open. By default, a form that is named Form1 is created.

7. In Project Explorer, right-click the Form1 form, and then click View Code.

8. Paste the following code in the code window of the Form1 form:

   Dim cn
   Dim rs
   
   Private Sub Form_Load()
   Set cn = CreateObject("ADODB.Connection")
   cn.Open "Provider=SQLOLEDB;Pwd=<password>;UID=<user name>;Initial Catalog=pubs;Data Source=<data source>"
   cn.CursorLocation = 2
   Set rs = CreateObject("ADODB.Recordset")
   rs.Open "select * from jobs", cn, 1, 3
   rs.MoveLast
   rs(1).Value = "Test"
   rs.Update
   End Sub
   

   Note password, user name, and data source are placeholders for the password, the user name, and the data source for your environment.

9. On the Run menu, click Start. You notice the error message that is mentioned in the "Symptoms" section.