PRB: Error "Cannot Update the Cursor" When You Modify Visual FoxPro Tables (294469)

MORE INFORMATION

You can use the Execute method (with Data Access Object or Microsoft ActiveX Data Objects libraries, for example) to execute Action queries on the Connection object. The following sample code uses the ActiveX Data Objects (ADO) library to reproduce the above-mentioned error. The sample code creates a test Visual FoxPro table named T1.Dbf, and then uses the INSERT SQL Action Query to add records.

Steps to Reproduce Behavior

1. Open a new Visual Basic standard EXE project. Form1 is created by default.
2. Set a reference to the Microsoft ActiveX Data Objects library.
3. Place two command buttons (CreateTable and ADOExecute) on Form1.
4. Add the following code to Form1:

   Dim conADO As ADODB.Connection
   
   Private Sub CreateTable_Click()
   
       conADO.Execute "CREATE TABLE T1 (col1 Int, col2 Int)", , adExecuteNoRecords
       MsgBox "FoxPro file created."
       
   End Sub
   
   Private Sub Form_Load()
       Dim strCon As String
       
       CreateTable.Caption = "Create FoxPro File"
       ADOExecute.Caption = "Execute Action Query"
       
       strCon = "Driver={Microsoft Visual FoxPro Driver};" & _
                "SourceType=DBF;" & _
                "SourceDB=" & App.Path & "\;" & _
                "Exclusive=No;"
                    
       Set conADO = New ADODB.Connection
       conADO.Open strCon
   
   End Sub
   
   Private Sub ADOExecute_Click()
       Dim strSQL As String
       Dim numRec As Integer
       
       strSQL = "Insert Into T1 values(1,100)"
   
       conADO.Execute strSQL, numRec, adExecuteNoRecords
       
       MsgBox "Records Affected = " & numRec
       
   End Sub
   
   Private Sub Form_Unload(Cancel As Integer)
       conADO.Close
       Set conADO = Nothing
   
   End Sub
   					

5. Run the project, and then click Create FoxPro File.
6. Click Execute Action Query, and notice that it executes successfully.
7. Select the Read-Only check box for the T1.dbf file.
8. Click Execute Action Query again, and you receive the above-mentioned error.