So, if yours doesn't, that's just weird :-\ Do you think you could send me some of your work so I can see better?
I can post all the code that I have it isn't very much, I don't think you will be able to access the database. Record Source = "SELECT * FROM Parts WHERE Manufacturer LIKE """ & txtterm. Refresh End Sub Private Sub cmdpnum_Click() Adodc1.
Value End Sub Private Sub dg_Persons_Before Col Update(By Val Col Index As Integer, Old Value As Variant, Cancel As Integer) Msg Box Col Index End Sub Private Sub dg_Persons_Click() If dg_Persons.
Value) End If End Sub Private Sub Form_Load() ' dg_Persons.
When I enter data into it, skipping the autonumber field, it DOES automatically put the autonumber in.
I think you'll be opening a forward-only recordset by default.
Trying to do an efficient delete of multiple records in an ADO recordset bound to a Data Grid control, and populated from an MS Access 2000 database. This will open and set everything'Dim con Obj As New ADODB. Data Source = rs Objdatagrid.refresh'''''''''''''''''''''''' 2. I'd like to sort on two other fields, Date Time and Document, which taken together form unique records, and then renumber the Index field.2) Then I'd like to do the equivalent of Access' "Compact and repair database" tool. Again thanks, Dan Well, for the compacting you can use JRO (Microsoft Jet And Replication Objects). So what I want to do is simply renumber the records after deleting the old ones. Trying to do the same thing with the data-bound control produces the same error on update that deleting a record did.
It confuses me to see the 'write to XML' example create three files.
The client side is vb6 and using Dcom dll's hosted on the db server.