>It's in a Button Click Event.
>I removed it and the function now functions correctly...
>
>The code really looked exactly like:
>
>THISFORM.lEditMode = .F.
>THISFORM.lNewOperation = .F.
>NODEFAULT
>THISFORM.ShowGets()
>
>I was just generalizing for simplicity.
Just asking because there are uses for NODEFAULT - e.g., in Codebook's Quicken(r) style date textbox it's useful to turn off the annoying beep or in a KeyPress event to cancel a keystroke.
But in a Click() - yeah, that doesn't do anything at all.
I wonder if the developer was confused thinking that it would stop any inherited custom code from firing, not realizing that he had already done that by adding code at all.
Insanity: Doing the same thing over and over and expecting different results.