Hi Edward;

I agree the names should be different, but this is a conversion project and they are the same. The big question is why does the report the function call use the the procedure in the program but if that program calls a form that has the report form call, it goes all the way back to the procedure file. I thought the procedure file was last on the stack and that the function look up went up the program tree looking for a calling program that had the required function call.

Bob


>>Here is an interesting problem. Here are the salient points.
>>
>>[1] Within a program file I have a function called GetPend.
>>[2] Also within this program file is a report print routine.
>>[3] The report has a call to GetPend()
>>[4] One of the global procedure files (SET PROC TO...) also has a function called GetPend
>>
>>Now, if I run the report from the program file with
>>REPORT FORM .......
>>it all works fine and calls the GetPend function from the current program file.
>>
>>However, I have a standard Reporting form which I normally use so the user can select View, Print, print to file, change printers etc. It takes a report form as input.
>>
>>If I do a DO FORM Reporter WITH "" then the function that is called is the one from the global procedure file, not from the current program (that has the DO FORM in it).
>>
>>This seems to ignore the procedure hierarchy where the function in the current program should be in the call stack and should be called.
>>
>>Does anyone have any ideas why this happens and what can be done to avoid it?
>>
>>Bob
>>
>>boblucas@minerva.ca
>
>I thing the normal way is to use different names for different procedures.