>Hiya George!
>
>>>>I can understand that, but then you have to also shut off editing the data in one of the two forms. Just IMO I think it easier to not allow the second one to open in the first place.
>>>
>>>Why do you have to shut off editing? The two forms work in almost all respects as two separate users. I mean, in a multiuser system, you don't have to shut off editing for one of the users! Sure, the users should be aware that two users - or two forms - editing the selfsame record can ocassionally lead to conflicts, ocasionally forcing one of the the user to undo a few changes.
>>
>>Hilmar,
>>
>>Well, in a multi-user system, unless you're using pessimistic buffering, the "last man standing" rule applies.
>>
>>On the user side, however, allowing the user to have two of the same forms open at the same is trouble, unless you place a REQUERY() command in the form's Activate event. Unfortunately, this can be a problem performance wise.
>
>I suggest you're correct that there should be some means of preventing the scenario you describe. The same user on the same workstation should not edit the same entity in different forms. I disagree that preventing a second instance of the form is the way to do that. Power to the user! When and if they navigate in the second instance to the same record, inform them.
>
>I watch the workflows in places like Home Depot. I'm in line while the person ahead of me needs a price check. Why can't they fire up another instance of the invoice form, complete my sale, and go back to the other guy when his price check comes back?

Mike,

Maybe it's a blind spot of mine. Most of my work is in a "heads down" evironment.

BTW, love the sig block.