ADO and updating records

tcarnahan · June 9th, 2004, 07:05 PM

My brief excursion from DAO to ADO using a JET backend on the server was less than rewarding. I had a continuous form that pulled data from a single table in the backend. Given those conditions, I would have thought that the recordset behind the continuous form would have been updateable ... it was not.

Unfortunately, I don't have the code any more. I was advised by an MVP on another newsgroup that a Jet backend is NOT updateable using ADO. I am using Access 2000 (at work).

Would anyone care to share their experiences with this type situation?

Thank you ahead of time for any help you can give! :)

--- Tom

Steven · June 10th, 2004, 01:39 AM

IT all depends on how you open your data.
If, for example you do:

Code:

rs.LockType = adLockReadOnly

Then, true, the data won't be updateable
But if you open a recordset like:

Code:

rs.Open sSQL, YourConnection, adOpenKeyset, adLockOptimistic

Then, as Captain Planet would say - "The Power is Yours"

I am a loud man with a very large hat. This means I am in charge

tcarnahan · June 11th, 2004, 09:26 AM

I will have to try this ... my recollection of trying this being linked to a single table in a JET 4 backend was that it would not work. I used the recordset as the source of my continuous form ... I could refresh the form, but not edit and update a record. I wonder if I should have used an unbound form and tried some type of word around like that.

Would you have an example of some code ... dim statements, setting the connection string, etc that would illustrate this? I must have gotten so frustrated, I deleted my examples.

Thanks,

"ADO Newbie"

--- Tom