I have a record lock bit on as a field in a table and I use this lock to determine if the field should be enabled on a form or not to allow or disallow editing. This seems to bog the program down considerably. Is there a more efficient way?
the problem is most likely not the bit field in the database, but how you are accessing the field.
this is still inefficient. what happens when the next set of requirements says, oh and we need to lock field x as well. now you need to modify the code and the database schema.
without knowing more about the requirements of why the field needs to be locked and what the specs are to (dis)able the control I can't think of a better way to update the record.
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.