alvechurchdata
Programmer
We have a VFP8 report which works when the exe is called from the development environment but fails with "Their_ref not found" when the exe runs on the user's PC. "Their_ref" is a field of the cursor being printed on the report.
I have single-stepped the code and checked that "Their_ref" does exist in the cursor, the cursor is the current work area, and there is not a memvar named "Their_ref" in my development environment. I have added various debugging messages just before the REPORT FORM in the exe and confirmed that the right work area is selected and that the field "csrParts.Their_ref" does exist and that it does have a valid value.
We made no progress until I put a BROWSE into the code so that we could look at the data on the user's PC. This fixed the problem. The browse window appears, the user presses ESC to close it, and the report prints correctly. If I RELEASE the browse in code or if I stuff ESC into the keyboard buffer to close it then we go back to the original error message.
The only solution I can find is to show a Browse window and have the user close it manually. It doesn't matter whether they click the x widget with the mouse or press ESC on the keyboard.
The report is a new one I've just added to an app written perhaps ten years ago. Can anyone suggest what is going on?
Geoff Franklin
I have single-stepped the code and checked that "Their_ref" does exist in the cursor, the cursor is the current work area, and there is not a memvar named "Their_ref" in my development environment. I have added various debugging messages just before the REPORT FORM in the exe and confirmed that the right work area is selected and that the field "csrParts.Their_ref" does exist and that it does have a valid value.
We made no progress until I put a BROWSE into the code so that we could look at the data on the user's PC. This fixed the problem. The browse window appears, the user presses ESC to close it, and the report prints correctly. If I RELEASE the browse in code or if I stuff ESC into the keyboard buffer to close it then we go back to the original error message.
The only solution I can find is to show a Browse window and have the user close it manually. It doesn't matter whether they click the x widget with the mouse or press ESC on the keyboard.
The report is a new one I've just added to an app written perhaps ten years ago. Can anyone suggest what is going on?
Geoff Franklin