Bruce,

>Can't describe a problem until you understand what the problem is.

You can give a better description of what appears to be not functioning like you expect it to behave. Give us the same kind of information you need your end-users to give you to explain a problem they are having with your program so that you can debug it.

>If I have no program running and DO FORM from the command prompt the forms work correctly.
>
>When I call it from a program or from the command window from a supended program the form appears to be read only and no buttons work and you cannot edit any of the input fields.
>
>What code setting and/or form setting could cause this behavior?

I can not think of anything that would cause the behavior, there is no setting that would have this kind of effect. You should look at whatever SET statements you've done in the program(s) that calls the form and compare those to the SETs in your default VFP environment.

What are the overridden properties of a control that is not working (ie everything that is bold on the property sheet? Are you using VFP BaseClasses for these controls or FFC subclasses or some other subclasses?

When you say you can't edit, do you mean any characters you type give you a beep and the character doesn't appear in the field? do you mean the control is disabled so that you can't even get focus into the control? do you mean that you can change the value of the control on the form but that the editted value doesn't make it to the ControlSource of the control? These are the kinds of details we need to be able to efficiently help you out.