Kbase 33401: _Osprint will not use the specified font settings when used with the AppServer
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Solution ID: P3401
FACT(s) (Environment):
Progress 9.x
Windows NT 32 Intel/Windows 2000
SYMPTOM(s):
_Osprint will not use the specified font settings when used with the AppServer
Running the _osprint in batch mode using prowin32 -b on the same Appserver machine works and the specified fonts are used.
CAUSE:
The Fonts section of your ini file (or the registry) is not loaded in character interfaces, so the font number passed to _osprint.p is ignored since there is no font table in which to look it up. ProPrint asks the client for the font description (in this case the client returns nothing); it doesn't look it up in the Fonts section itself.
There is no workaround for this limitation in character mode versions of Progress running on Windows.
The _proapsv.exe is an executable stripped of any user interface. It has less user interface capabilities than the _progres.exe (character client) executable
The prowin32 on the other hand has more capabilities and more of an interface. Using -b just suppresses the interface from being displayed. Therefore the fonts will be picked up.
FIX:
Run _osprint in batch mode using prowin32