This is a classic implementation of a semaphore, with the RESERVE table data being the semaphore. And so... well, I guess it kinda sorta depends. Are you having any problems with this current mechanism? Are you (or, more importantly, your users) disatisfied with the current process? I guess I'm thinking that "if it ain't broke..."

If so, what are those problems and/or disatisfactions?

It doesn't sound like this is a high-volume application, so what you've got is otherwise probably fine - and thus mebbe you should spend more time on other parts of the app?

Whil