The age of dgillz's ddfs is not important, as the table structure has not changed since the inception of Macola for Windows. I developed a set a few years ago along with a report, however I did this with another company and no longer have the solution in my posession.
Once you have dgillz's ddfs you will find a screen id, screen name, screen number, and screen data field. The screen id field is 8 characters and contains the name of the screen that is used by Macola designer to reference the field.
The screen name field is 10 characaters long and contains the name of the user that the screenset applies to. If there is no customization then this field value will be "MACOLA" for default, a group name or Macola user name. In addition you may find "MACOLAED". In Macola prior to 7.6.200 this is the screen name that is used when a source code enhancement is in use for the module in question. Starting with Progresion 7.6.200 any screenset named "MACOLAED" is used regardless of source code enhancements. (If you want to develop a screenset that you don't have to copy to everyone this is a good way to do it. You would need to develop the custom screenset under any names but "MACOLA" or "MACOLAED" and then copy it to "MACOLED" after completing your changes, but I digress).
The screen number field contains a number of 1, 2, or 3. Each screen can take up to 3 rows of data in the database and this field just indicates the order in which the screen designer concatenates the data in the next field.
The screen data field is either 3000 characters long and contains binary information that represents the screen design.
That being said, in your report make sure you filter for only screen number 1 (you can ignore 2 and 3) and make sure you properly handly group and "MACOLAED" screen names and you have yourself a report.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.