ID: Q125308
2.60 2.60a WINDOWS kbtool kbenv kbbuglist
The information in this article applies to:
A report containing a variable name that has more than 10 characters can cause a general protection (GP) fault when called from an executable created with the FoxPro for Windows Distribution Kit. The GP fault occurs even if no fields are present in the REPORT FORM.
The .EXE works properly when called from the Command window in the development environment, but will cause a GP fault if run outside the development environment from a directory where FoxPro is not installed. The .EXE works correctly when run from the directory in which FoxPro is installed.
Use report variable names that have 10 or fewer characters.
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
1. Create a new report, and make a quick report.
2. Add a report variable that has a name containing 11 or more characters
and store "" as the value.
3. Save the report as <formname>.FRX, and close it.
4. Create a new project, and add the report to project.
5. Create a program (.PRG file) that contains this line:
REPORT FORM <formname> TO PRINTER
6. Add the .PRG file to the project, and set it as the main program.
7. Build the .EXE. Then exit from FoxPro, and run the .EXE file. Make sure
the .EXE file is in a directory other than the FoxPro directory.
8. The result will be a GP fault.
KBCategory: kbtool kbbuglist KBSubcategory: FxtoolDk buglist2.60 buglist2.60a Additional reference words: 2.60 2.60a FoxWin GPF
Keywords : kbVFP260bug FxtoolDk kbvfp260abug kbbuglist
Version : 2.60 2.60a
Platform : WINDOWS
Last Reviewed: February 15, 1997