Because the layouts table does not maintain itself, it must be manually “cleaned.” When you use SysManager > Activities > Pack Up All Layouts, the first result is that you erase the entire contents of the layouts table. SysManager then prompts you to select the Layouts folder and after you select the Layouts folder it then reads and writes the entire contents of the Layouts folder to the layouts table. At this point you have a layouts table that contains only entries from what is in the Layouts folder at that moment. Layouts and images that are stored in sub-directories in the Layouts folder are also packed along with a description of the exact path – if the path doesn’t exist in the Layouts folder on the salespoint, the appropriate sub-directories are automatically created when the layouts table is unpacked by PrintEZ application and the corresponding layouts and images are unpacked into those sub-directories.

 

Note: Activities > Pack Up All Layouts also packs up the image files that are referenced in the Graphic layouts in the Siriusware\Layouts folder. If they are not referenced by a layout, they are ignored. Images are always reference by graphic layouts – they are never copied into the layout itself. If a layout references an image file that is not in the expected place in the Layouts folder, you get an error message similar to the following and the packing process completes.

 

 

Note: Activities > Pack Up All Layouts ignores any FoxPro labels files (.lbt/.lbx). These are used from SysManager and ReportManager for creating mailing labels, so are not needed at the salespoints.

 

Layouts are never edited directly on the salespoint because they are simply overwritten the next time the layouts table in unpacked. The following subdirectories are in the Siriusware\Layouts folder:

 

If you use .INI settings to reference layouts (such as receipt=), then these layouts are ignored in the packing and unpacking of layouts because the layouts table has no knowledge of them. If you would like to include these layouts in the usual layouts processes, then store the masters in the Siriusware\Layouts folder and reference them from a “dummy” item that doesn’t actually use them. In this way they are included in the packing, unpacking and updating processes because they are stored in the layouts table.