>>VFP ships with the Label/Report Wizard for defining custom labels. From my current analysis of the code, the tool is derives the label layouts from a table of codes (englbls.data field). I am currently looking into how this tool works to generate the label layouts. Has anyone already done this? If so, can you share your code that extracts the label definitions and then generates a LBX report? Thank you.
>
>Have you looked at the AddLabel application to see how it works?

Yes -- it simply adds entries to the existing tables (actually stored in the registry -- the first time you run the wizard it adds the entries to the registry; the wizard calls the addlabel.app to add new definitions). The AddLabel app just adds the label dimensions/column count as a definition; it is still the Wizard that actually creates the label report from the definition.

I have begun to decipher the wzreport project and the main engine is in the rptengin.prg file but the process seems to be quite awkward and no documentation in the program as to how the properties are used. It seems to read the standard LBX as a style into different property values as record types. These are then modified based on the new definition and then a new label is created. It is how the definition is applied that I am most interested in if anyone has done this already. There is a lot of manipulation occurring and I want to be sure not to miss anything. My need is for a simple engine to print a memo field onto a label for any Avery label; so I have one field on the label and then the column count, height, width, etc then needs to be defined based on a selected label definition.