>>>Hi Ernie,
>>>Two points :
>>>1. In format mask you use KZ. Z for zero, is this a numeric value ? For tel. numbers it's convenient to have char values and format mask as KR.
>>>2. SET CONFIRM is scoped to current datasession. So if globally you have *set confirm on* and you set it on entry.prg *off* it won't *set confirm off* in form loading with a DE. It will be set back to *on*. In DE, beforeopentables event add *set confirm off*
>>
>>Hi Cetin,
>>
>>Well I hope you're wrong. I have confirm set on as the default in tools-options. In the Form.Load I have
>>"Set Confirm Off", and when I run the form, Confirm is indeed off. At first I thought that it was on when the
>>form was active (see another branch from your message), but I just discovered that I was not looking at the
>>correct data-session.
>>
>>If I'm overlooking something, I would appreciate having it pointed out.
>>
>>Bill
>I think I should clarify it. First off all documentation says it, not me. Create two forms one with a private data session. Set confirm on in command window, call the forms, while the one with the default datasession has confirm on, the other has set confirm off.

Hi Cetin,
Hope I'm not being a pain in the ***.
I think we're having a communication problem.
in #2. above, I interpreted that to mean that if I set "set confirm off" in the Form.Load event it will reset
to "on" after the Form.Load, so put it in the DE.BeforeOpenTables instead. I now read again and I think you're
saying that if I "set confirm off" in a PRG that launches the form, that it will get reset to "on".
In conclusion, I hope you agree that it doesn't make any difference which method it's in (Form.Load or
DE.BeforeOpenTables). Either one will work.

Bill