Run4YourLives
Programmer
After running an SQL UPDATE statement on a .btr file, the records affected are no longer editable, returning messages in the parent application consistant with the record being locked.
I am assuming that, since records that weren't updated are not affected, the .BTR table thinks that the SQL statement still has the records "open", and has marked them as "locked" somewhere.
My question is twofold: 1. How can I force the records to believe that they are no longer "open", or locked by anything, (because they aren't) and 2. How can I avoid this happening again, while running SQL updates from VB6 on a Pervasive 2000i database?
Thx in advance!
I am assuming that, since records that weren't updated are not affected, the .BTR table thinks that the SQL statement still has the records "open", and has marked them as "locked" somewhere.
My question is twofold: 1. How can I force the records to believe that they are no longer "open", or locked by anything, (because they aren't) and 2. How can I avoid this happening again, while running SQL updates from VB6 on a Pervasive 2000i database?
Thx in advance!