Kbase P10626: Error (4499): Caused by a gap in the defined font number sequence.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Verified
FACT(s) (Environment):
Progress 8.x
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
SYMPTOM(s):
Error 4499 when running/opening application
** Font <font-number> not in Font Set. (4499)
Using an INI file instead of the registry
Font <font-number> is defined in the Fonts section of the ini file.
Progress is correctly started with '-basekey INI -ininame ...'
CAUSE:
The .ini is malformed, therefore Progress cannot correctly read the Fonts section.
One possibility is that a font key is missing or mistyped in the Font section of the .ini file. Keep in mind that the list of font keys can be in any order, but have to be a complete sequence. For instance the following:
<default fonts>
Font8=<whatever>
Font9=<whatever>
Font13=<whatever>
Font10=<whatever>
Font11=<whatever>
Font12=<whatever>
is a complete sequence and will load all fonts. However, if one of the entries is missing, only the fonts up to that entry will be loaded. For example, if the list is:
<default fonts>
Font8=<whatever>
Font9=<whatever>
Font13=<whatever>
Font10=<whatever>
Font12=<whatever>
only fonts from 0 to 10 will be loaded because font 11 is missing. Trying to use font 13 in the application will result in the error because it isn't loaded, even though it itself is properly entered.
FIX:
Revise your .ini file to ensure that there is no gap in the defined font number sequence.
Alternatively take PROGRESS.INI from the %DLC%\bin directory as a template and change it to recreate your .ini file ensuring that there are no gaps in the defined font number sequence.