Well, cflock really shouldn't be used for database work IMO. Not unless you are using a desktop database like Access. Probably what you need is a simple check-in/check-out system. So if userA wants to change the schedule, they do a check-out for modifcations. Then userB or userC, couldn't make modifications until userA commits their changes. You might be able to simulate this with cftransaction (level serializable), but I don't know enough about it to know what effect that would have on the rest of the application. As I understand it serializable single threads the process, so it is possible other queries on the schedule table might be forced to wait until the updates are done. But if you only have 5 or 6 updates per day it might not be a big issue for you. Just things to keep in mind ..