qpp_TempSaintsExceptions.txt contains date-specific records from the legacy saints/namedays exceptions temporary table prepared for diary generation.
Unlike the regular saints table, each record identifies a complete date, including its year.
The legacy saints/namedays exceptions mechanism is deprecated. Current scripts can use “Combine with Holidays Set below” in Saints/Namedays Options. That route uses holiday data and should also be investigated in qpp_TempHolidays.txt.
Column |
Interpretation |
CountryID |
Internal set ID for the exception record. |
Date |
Q++Studio integer date, measured in days from 30 December 1899. Keep both the stored value and the converted calendar date when reporting a match. |
Sex |
Stored gender code. Use the actual implementation or documented mapping if decoding is necessary. |
Value |
Stored replacement name or text. |
GraphicsPath |
Stored graphics path, if any. |
NoSite |
Site identifier, preserved as text. |
An Empty Export Can Be the Correct Result
The supplied example has the column headings, no data rows, and the footer “End of export: 0 records.” This is a complete empty export of this temporary table. It does not show a failed scan, an empty regular saints list, or the absence of holiday-based replacements.
In the simple run, the accompanying regular saints export has 366 rows. In the complex run, both exports contain zero records. These are separate data sources: a script can have a regular saints list and no legacy exceptions, or require neither.
1. Establish whether the affected DiaryGridLine enables the legacy “Use Saints/Namedays Exceptions” option. If it instead uses a holidays set, examine that route and its effective selection.
2. For the legacy route, look for the exact NoSite, CountryID, and Date. A matching month and day from another year is not a matching exception.
3. Compare the exception Value with the regular saints row and the script options. Under the legacy option, an applicable exception replaces the regular name. The documentation also describes its precedence over the holiday-combination options on that date.
4. Confirm the resulting text or instruction in qpplog.txt or the output. A record being available does not establish that the relevant option was enabled.
A suitable conclusion for the example is: “No legacy saints-exception records were exported. Check whether this script uses that legacy option or uses holiday-based replacements.” Do not recommend filling this table simply because it is empty, and do not describe a particular date as missing until the relevant set and mechanism have been identified.
See qpp_TempSaints.txt for regular month/day entries and the diagnostic-files overview for export-format details.
Topic 189920, last updated on 22-Oct-2026
