Thanks for your response Whil,

>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..."

I'm not having any problems and my users are not dissatisfied. As I said, I'm rewriting the system in VFP, and got to thinking that there might be a better way and someone may have suggestions about it.


>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?

You're right, it's not a high-volume app...thanks again for your input - I really do appreciate it. J