>/ 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
>
>Well, well... are you sure that the program, which called the form,
>didn't exit already? Try to see the call stack from the debugger, and
>place a breakpoint into the GetPend procedure in the procedure file (the
>one which gets called) and see if the routine which called the form is
>still up and running.
>
>If it is running, I'm rather confused, too ;( - this behavior contradits
>all the known behaviors in all the known versions of Fox. Is it possible
>that calling a form shortens up the call chain?


The default behaviour is for the current program to look within itself for the function (which forms now don't have) and to look next in the procedure file(s) and if not there then up the program stack. Therefore, my function would have been called after the check in the procedure file. If I don't use a form, then the function exists in the current program and there is no problem. I thought the procedure library came LAST but it actually comes Next after the current program.

This is good to know! (this information is from Randy Pearson. Goes to show that we should not always rely on what we think we know) This goes to my second rule of programming: "If you've done everything right and it still doesn't work then something you did right is wrong."

Bob