D
Dave Rudolf
Hey all,
I have a hunk of VB code that is modifying records in an Access 97 database
through an ODBC driver. The code looks like this(where adoWorkOrderWrite is an
ADODC control):
adoWorkOrderWrite.Refresh
adoWorkOrderWrite.Recordset.Find ("MPWOID = '" & cmbWorkOrder.Text & "'")
If Not adoWorkOrderWrite.Recordset.EOF Then
adoWorkOrderWrite.Recordset!WO_Status = WORK_ORDER_STATUS_CLOSED
adoWorkOrderWrite.Recordset!Date_Complete = Now
adoWorkOrderWrite.Recordset.Update
wroteWO = True
End If
Now, when the above code is run, I get a dialog popping up saying:
[Microsoft][ODBC Microsoft Access Driver] Operation not supported on
replicable databases that have not been converted to the current version.
I get the same error if I try to add records (i.e., if I do an AddNew before
setting any fields in the code above). The Microsoft knowledge base says that
this was an intended "feature" of the ODBC driver for Access, and that I
should instead use the Jet 3.5 driver with my ADODC. Unfortunately, that's not
really an option, as the database may change to SQL or something like that in
the near future and I don't want to have to recode the system.
Now, I can happily write to other tables in this same database. So, can anyone
hint as to why this one table is causing me grief?
Thanks.
Dave
I have a hunk of VB code that is modifying records in an Access 97 database
through an ODBC driver. The code looks like this(where adoWorkOrderWrite is an
ADODC control):
adoWorkOrderWrite.Refresh
adoWorkOrderWrite.Recordset.Find ("MPWOID = '" & cmbWorkOrder.Text & "'")
If Not adoWorkOrderWrite.Recordset.EOF Then
adoWorkOrderWrite.Recordset!WO_Status = WORK_ORDER_STATUS_CLOSED
adoWorkOrderWrite.Recordset!Date_Complete = Now
adoWorkOrderWrite.Recordset.Update
wroteWO = True
End If
Now, when the above code is run, I get a dialog popping up saying:
[Microsoft][ODBC Microsoft Access Driver] Operation not supported on
replicable databases that have not been converted to the current version.
I get the same error if I try to add records (i.e., if I do an AddNew before
setting any fields in the code above). The Microsoft knowledge base says that
this was an intended "feature" of the ODBC driver for Access, and that I
should instead use the Jet 3.5 driver with my ADODC. Unfortunately, that's not
really an option, as the database may change to SQL or something like that in
the near future and I don't want to have to recode the system.
Now, I can happily write to other tables in this same database. So, can anyone
hint as to why this one table is causing me grief?
Thanks.
Dave