A report that is transported from FoxPro 2.x for MS-DOS causes problems in Visual FoxPro (256156)
The information in this article applies to:
- Microsoft Visual FoxPro for Windows 3.0
- Microsoft Visual FoxPro for Windows 3.0b
- Microsoft Visual FoxPro for Windows 5.0
- Microsoft Visual FoxPro for Windows 5.0a
- Microsoft Visual FoxPro for Windows 6.0
- Microsoft Visual FoxPro for Windows 7.0
- Microsoft Visual FoxPro 8.0
This article was previously published under Q256156 SYMPTOMS
A report is originally created in FoxPro for MS-DOS and is transported to Microsoft Visual FoxPro. The report is problematic, possibly causing Visual FoxPro to crash or the system performance to degrade when it is run.
CAUSE
The report writer in Microsoft FoxPro for MS-DOS contains an interface that allows the developer to select a style for printing a selected field. The interface inputs values in a memo field of the report (.frx) called "style." Values that the interface can input are:
- B - for Bold print
- I - for Italic print
- U - for Underlined print
- R - for Raised face (Superscript) print
- L - for Lowered face (Subscript) print
- J - for right Justified print alignment
- C - for Centered print alignment
In the event that a report .frx file contains any style code or codes other than those listed above, the report can cause system problems when it is transported to Microsoft Windows and edited within or run from Visual FoxPro.
RESOLUTION
Any style codes other than those listed in the "Cause" section of this article should be removed.
STATUS
Visual FoxPro for Windows adds additional fields to a report .frx file that store font and formatting information. For this reason, the report writer of Visual FoxPro does not utilize the style field of the report .frx file. However, the style field is present for backward compatibility and Visual FoxPro does read the style field (and all the .frx file information) when:
- Saving a modified report
- Closing a report in design mode
- Rendering a report at run time
One particular activity that demonstrates the adverse impact of the unexpected style information is to copy objects (copying to and pasting from the clipboard) from one report to another. After this is done, close one report and then the other. This step might need to be repeated two or three times and then the following error can occur:
The instruction at "memory address" referenced memory at "memory address". The memory could not be "written".
After this message is displayed, Visual FoxPro shuts down.
A number of third-party products are available as extensions to the FoxPro for MS-DOS report writer. These usually come with PDSETUP (Printer Driver Setup) information that allows for printing special character sets (such as bar codes, and so forth) in MS-DOS. These can input values in the style field of the report .frx file that are not listed in the "Cause" section of this article.
Modification Type: | Major | Last Reviewed: | 2/11/2005 |
---|
Keywords: | kbprb kbReportWriter KB256156 |
---|
|