That is also what I thought. But I've tried many syntax combinations for the recordset cursortype, cursorlocation locktype update type (including those you mentioned), modifying rs.fields("field") vs bound textbox etc, but to no avail. Maybe in the next ADO version...
Ok, thanks. That's unfortunate. Can't leave it open due to WAN limitations and the users tendacy to keep the program open all day, and tooo many fields to track for changes (sounds like an ordeal). Guess I'll try to save off the employee # when they hit the edit button to unlock the textboxes...
Using vb6, ado2.5 & sqlserver 7.0, I get the recordset(rst) with adUseClient, trying various combinations of keyset/dynaset/static/unspecified and various locks, populate form textboxes with fields then set the rst.activeconnection = nothing and the textboxes datasource=rst and datafield =...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.