I failed to mention that if I remove the DODEFAULT() call in the form's refresh method, the only syntax error message I get is on the line in the calling form that executes the DO FORM command to run my problem form. and, as before, the problem form appears on the screen and is apparently functional.

Jim

>>Try to put some breakpoints in Activate method then in form's Refresh.
>
>As you suggested, I put breakpoints in the form's activate and refresh methods. Since I have no code in there right now,I have added DODEFAULT(), and put the breakpoint on those. It stops at both breakpoints.
>
>It proceeds OK from the form.Activate breakpoint, stopping next at the form.Refresh breakpoint. If I try to step over that, I get a syntax error. If I click Ignore, I get a syntax error on the line in the calling form that contains the DO FORM command that is executing my problem form. Note that the problem form is visible on the screen and apparently functional.
>
>What is causing these "syntax errors". No information in the error message.
>
>Jim
>
>>
>>>I have a form that is called as a subroutine from another form:
>>>
>>>DO FORM SetupProjSessions WITH nProjectID TO lResult
>>>
>>>The WindowType property of SetupProjSessions form is Modal.
>>>
>>>When I run the main form and execute the DO FORM statement, the SetupProjSessions form appears the the screen, but I get a "syntax error", with no other error information.
>>>
>>>Under the debugger, I can see that SetupProjSession.Init runs to completion. I even added an explicit RETURN .T. statement and step through that.
>>>
>>>The next thing that executes is a refresh method of a container (a supermover object) on the SetupProjSessions form, and then the refresh method one of its listboxes. When I step out of the refresh method of the listbox, I am back in the calling form on the line following the DO FORM call, with the "syntax error" message on the screen.
>>>
>>>If I click Ignore to the 'syntax error' message, the SetupProjSession form continues to work.
>>>
>>>I would appreciate suggestions on how to debug this.
>>>
>>>Thanks,
>>>Jim