BUG: Crash Updating Linked Table with ADO2.1/Jet 4 OLEDB Provider (235433)

MORE INFORMATION

Steps to Reproduce Behavior

  VB application (Client machine)
                |
                |--(Jet 4 OLEDB Provider)--> Linked Table in Access (Remote machine) 
                                                       |
                                                       |--(ODBC DSN)--> SQL Server Table (Remote machine)
				

1. Create the following SQL Server table (server machine):

   CREATE TABLE dbo.pepers (ID int NOT NULL Primary Key,
   	TestField char (220)) 
         GO
   					

2. Insert ID # 1920 into the table.
3. Create a DSN going to the pepers table on the server machine.
4. Create a new linked table in an Access database that goes to pepers table. "dbo_pepers" would be created by default.
5. Create a new Visual Basic 6.0 Standard EXE project (on client machine) using the following code:

   Option Explicit
   Dim cn As New ADODB.Connection
   Dim cmd As New ADODB.Command
   Dim sqlStr as String
   
   Private Sub Command1_Click()
   
   cn.CursorLocation = adUseClient
   
   With cn
       .ConnectionString = "Data Source= <path>\<Access database>"   
       .Provider = "Microsoft.JET.OLEDB.4.0"
       .Properties("Prompt") = adPromptComplete
       .Open
   End With
   
   ' The following statement would update 220 characters on the char (220) TestField
   sqlStr = "UPDATE dbo_pepers SET TestField='" & _
                   "send10char send10char send10char send10char " & _
                   "send10char send10char send10char send10char " & _
                   "send10char send10char send10char send10char " & _
                   "send10char send10char send10char send10char " & _
                   "send10char send10char send10char send10char'" & _
                   "WHERE ID = 1920"                   
   
   cn.Execute sqlStr   ' <--- crash occurs here
   
   cn.Close
   
   End Sub
   					

6. Add a Reference to "Microsoft ActiveX Data Objects 2.x Library," and also place a Command Button on the form.
7. Click on Command1 button two to six times and the crash would occur.