🧠 What’s going on
TableFormats.csv is essential for the correct operation of the various costing tables and cutting list tables when inserted into MS Word templates. It has been observed that a crash can occur with a "Runtime" error from Roof Wizard if the tables and formats are not set correctly.
1️⃣ #1 - Problem
If you add a new table to a word template you must remember to add the display definitions to the table formats file that match the description of the format as defined in MS Word. If the table layout is not defined it causes Roof Wizard to fail while talking to the template and subsequently crashes the software with this error:
Make sure that all tables used in the Word templates has a definition in the TableFormats.csv file. The link provides more details.
For more details on setting up table formats, and how they work, please refer to the help files online:
2️⃣ #2 Problem
The runtime error and then a Roof Wizard crash was found after the user updated their PC to that latest version of Windows 11 (V23H2) and the corresponding latest version of MS Office with MS Word - specifically, Microsoft® Word for Microsoft 365 MSO (Version 2504 Build). He then copied all his current data files, job files and templates from his old PC to the ..\User folder on his new PC.
It turns out that Microsoft has changed the labels that define the various table formats in the new version of MS Word, and our user had an 'old' table format that is no longer available in the new MS Word. Without a definition, the table could be filled out but not re-formated, and this caused the Roof Wizard to crash. The TableFormats.csv file was updated to currently named table formats now available in MS Word and it all started to work again.
For more details on setting up table formats, and how they work, please refer to the help files online.
3️⃣ #3 Problem
It seems that the TableFormats setting for each table MUST match the number of columns for each table used. While trying to make it a 'catch-all' setup, this setting caused a crash because there were not enough settings or too many.
This is the ###PitchAreasTable, it has three columns:
Tableformats was set with just two column widths set:
and too many columns set:
And these both crashed the printing process.
Setting it up correctly for three columns as required for this table and it just works.
