That bring out some other concerns:
What do you do if the person that started the modification goes to lunch while his record is still not saved?

Then the person who wants to edit the record will need to go to their computer and save it. :) It's a small company, so I honestly don't think record contention is going to be a major factor.

What if the application need to be accessed by the web?
I know this is usually "famous last words", but I honestly don't see that happening. If it does, so much will need to be changed that this is a minor issue.

If you move the database to SQL Server (or another DB), you will have to implement your own pessimist locking rule, since you cannot lock a record in SQL Server (AFAIK).
Since I'm not locking the record, I don't see why this would be an issue.

I guess the only good answer will be given by the business rule of the client.
I don't think they care much how I do it. I'm doing it the same way SBT does, so they're used to that.

Thanks,

Michelle