Something is writing back to the form. Perhaps a view is loading, or a variable is being initialized that is being echoed to the screen. In the Load method of your child form be sure you have "SET TALK OFF". If you are using the dataenvironment, add the same code to the BeforeOpenTables event.

Oddly, this tends to show up only in compiled apps - forms that run just find from the command window get messy when compiled. I presume it has to do with different environment settings between development and EXE.

HTH
Barbara



>Dev Info
>--------
>I am using VFP6 service pack 3 on Win98, the application is n tiered using a business data object with several layers of subclassing to every control.
>
>Problem
>-------
>When I call a new form from this particular main form and then return to the main form, all the objects on the main form have jumped up by a line. In fact there is a white line at the bottom of the form. The original objects are ghosted in their original positions with the now incorrectly positioned objects above/over them. OK, so what I want to happen is for the objects to remain where I put them in the first place on the main form.
>
>
>Additional Info
>---------------
>The new form is called from a button click event with the form call method residing at the form level object. Another button on the form does the same form call method, but to a different form and does not demonstrate the same erroneous behaviour. I realise that this probably means the called form is at fault, I just don't know where to start looking. The load of the new form just creates some business objects and has no affect over the form display settings that I am aware of
>
>Lockscreen and Refresh states
>-----------------------------
>The calling main form has lockscreen set to .T. before the new form is called and a refresh is issued before the main form screen is unlocked, after the called form has been destroyed.
>
>Any help would be greatly appreciated.