Hi John,
If there's not much contention, I think that's a good way to go. Sometimes folks do a lot of programming for something that seldom, if ever, happens. If someone else trys the form, you can either give them a message that it's unavailable, or show it RO.
Remember, with Pessimistic Buffering, the Lock isn't applied until the user makes a change, so it's possible for user A to launch a form and then user B can still launch, edit, and save with user A now looking at stale data. (Speaking of something that seldom happens :-))

The one thing I don't like is when you show a form RO, there's no way for a user to tell who is doing the Supervisor work currently. It would be nice if the users could tell who is in the application. I use a UserHandler class that knows who is in the app. A user can then go to Help/About AppName/Users and see who is using the application.

Hi.,
> I have couple of forms used for custom setting for supervisor. These forms only allowed to be run in ONE of the workstations in netowrk. Once these forms launched, nobody are allowed to update the table.
> In the situation above, is it good to use FLOCK to lock the table from form.INIT until the form released? Or, do you have any other suggestion?
>
>Thank you