Hi Lee,
the problem of "SET STEP ON" left behond in code is serious (as I've learned).
Easier is the use of ASSERT .F..
If you put something like

IF _VFP.STARTMODE=0 THEN
 *If running from environment
 SET ASSERTS ON
ELSE
 *otherwise
 SET ASSERTS OFF
ENDIF _VFP.STARTMODE=0

, you will never need to care about lost breakpoints.

I use classes for the chance to inherit. Since I did'nt use dataenvironment and a lot of specialized form classes it's much faster to create a new class then a SCX because I always have to run through Obtions/Extras ... But this is not common as I understand other threads in UT.

>> Have you checked out the point where your code crashes?
>
>I can't because when the called form is activated 2nd time, VFP shut down and
>Return to windows...just saying..there is fatal trouble and close all jobs...

Lee, is there a posibility to add some breakpoint in form1 cmdbtn and then to single step with debugger until the system crashes? This might give you a better idea what's happening.
If you use ASSERT .F. you may easily run over the first click.

Lutz