>>I have seen many time that VFP is too quick for itself, so to say. Sometimes the only remedy is to add a little delay, like Inkey(0.2,'H').
>
>Any advice on where to add this? Before the call to Report Form? Perhaps is some sort of dummy function that would print blanks in the page header?
>
>Thanks......Rich

You get an error message that a variable is not found. If you know what variable is not found, I would add the delay just after this variable is initialized.

>>
>>>On a form is a container. When you click on the container it executes

>>>DO Print_Menu WITH 'PROJECT', 'GENEREP', thisform, [ADHOC] IN [Progs\REPORTMENU]

>>>
>>>This program creates a Popup menu with the list of reports. For each bar of the menu we have

>>>ON SELECTION BAR i OF popValues DO Print_Report WITH oCaller

>>>
>>>Print_Report hides the popup and calls a form. The form's init method generates some data and then

>>>REPORT FORM "Reports\" + lcReport + " " PREVIEW

>>>
>>>If I have a SET STEP ON anywhere in this process and simply hit the resume button everything works as desired.
>>>
>>>Without the SET STEP the report correctly appears on the screen. However, when the Print Button on the report toolbar is pressed, we get a Variable Not Found error.
>>>
>>>This was already in a TRY/CATCH block. So before the REPORT FORM line I created a variable with the value of ALIAS(). The first line of the CATCH block does the same thing. What has happened is that the ALIAS() changed (presumably when the Print button was pressed)
>>>
>>>Any suggestions on how to find the cause and/or fix the problem will be muchly appreciated.
>>>
>>>Please note.........VFP 8
>>>
>>>Thanks to all...................Rich