this is really strange. I got tired of stepping through it so I started deleting an object at a time and modifying it in between object deletes to see if I could at least isolate which object contained the offensive code. Once I deleted label1 it worked fine! Some hidden or junk code must have been in label1.

Tracy

>Just a SWAG, but since you have DODEFAULT() in the INIT, the following could cause the errors if the parent method code relies on the private variables. You declare a private variable, but when you initialize its value, you left off the "a". e.g., PRIVATE m.acondensed then you have m.condensed = .F. Private variables are a little different that local or public. They have to be initialized before they can be "seen" by other methods being called by this method. The same applies to your m.amultcopies and m.multcopies variables. Once the INIT finishes running, these variables would lose scope as well.
>
>>

>>PROCEDURE Init
>>	set STEP on
>>	*--To see datasession window, unremark the next two lines:
>>	*set step on
>>	*activate window view
>>	*UPDATES
>>	*03/06/2002 TCHolzer Modified to add user forms to ctrlset table
>>	PRIVATE m.acondensed,;
>>	        m.amultcopies,;
>>	        m.acn_name,;
>>	        m.acn_printer,;
>>	        m.acn_port
>>	m.condensed=.F.
>>	m.multcopies=.F.
>>	m.acn_name=""
>>	m.acn_printer=""
>>	m.acn_port=""
>>	DODEFAULT()
>>ENDPROC