I develop reports in Crystal for a large Windows desktop application. (Our application ships with about 1300 standard reports developed in Crystal.) The application uses the Viewer provided by the Crystal runtime engine in order to display the reports.
I'm experiencing a text clipping problem in my reports as displayed in the Viewer.
The problem occurs when I run our application under Windows 8.1 or Windows 10, but not under Windows 7. Below is a pair of screen shots. The first shows the problem under Windows 10. The second shows the same report under Windows 7, where the symptom does not occur.
Interestingly, the problem seems to occur only when the text is right-aligned in the text box, and only when the text includes three or more '1' (numeral one) characters in sequence. You can see in the examples above that dummy SSN values that contain substring '111' exhibit the symptom; others do not. These dummy SSN values are field objects in the report. Likewise, you can see in the examples above that static text values (eg: '1112') that contain substring '111' exhibit the symptom; other static text objects do not (eg: '112'). I've tested with various string values, but have been able to cause the symptom reliably only when my string contains '111'.
The problem does not occur in the Crystal designer (on my Windows 7 development machine), only when the report is displayed in the runtime's Viewer (on a Windows 8 or Windows 10 machine). I'm sorry that I cannot say whether the problem would manifest in the Crystal designer under Windows 8.1 or 10; I can't test for that.
We distribute and use the following runtime engine with our application:
SAP Crystal Reports runtime engine for .NET Framework (32-bit), Version 184.108.40.2065
That version of the runtime engine was used for the screen shots above.
I've also tested with the latest runtime engine (220.127.116.116) and the same symptom occurs, although it seems slightly less pronounced.
The font is Arial. I've also tested with Times New Roman, and the same symptom occurs although it is considerably less pronounced.
Both Arial and Times New Roman fonts were revised for the Windows 8 release. For instance, the version of Arial released with Windows 7 was v5.06; the version of Arial released with Windows 8 was v6.80. Arial is a default font for Windows, and thus has "locked font metrics" (see Fonts and text metrics (Windows)). Accordingly to the Microsoft page I've just cited, "because the reported values associated with these fonts are locked, there may be discrepancies between reported and actual font values." I read this as an indication that Arial (among other "locked" fonts) may report metrics about itself that are inaccurate given a history of revisions, redrawings, etc.
This report, like all standard reports in our application, is saved with the printer set to 'Microsoft XPS Document Writer', because that printer is generic and present on all Windows computers. (That generic setting precludes a lengthy timeout that would otherwise occur on a user's computer as it searches in vain for a printer that exists on my network (here at work) but not on the network in the user's workplace.) I've also tested by saving a different printer in the report (HP Officejet Pro 8600), and found that the symptom persisted.
I'm hoping that someone might have some insight into the cause of the problem and might be able to offer suggestions for a remedy.
To summarize my testing so far:
1. Problem occurs under Windows 8.1 or Window 10, but not Windows 7.
2. Problem manifests when a certain text string is used ('111').
3. Problem occurs whether the source object in the Crystal designer is variable (data field object) or static (text object).
4. Problem occurs in multiple versions of the runtime engine, including the latest.
5. Problem is particularly pronounced with Arial font.
6. Problem occurs for various printer designations in the Crystal file.
Thank you for your attention and assistance.