Typically to author a code generator for Delphi 7 that employs ADO is to have a file naming scheme that will accommodate the main line dialog the family id suffix is ml. The data module family id suffix is dmU. The component installer its family id suffix is pk. A component driver program with a family id suffix of dp. And finally the component tester and its family id suffix is cmpml. Any workbench units would have a family id suffix of wbU. Typically a batch file that would copy associated forms and Delphi complied units or dcu to a central repository. This approach lends itself to accommodate infinite components but maintain availability for seamless integration into multiple projects. A single entry int the IDE environment make all available component for use and reuse by any number of projects.
A set of skeleton programs that comprise the data grid, memo place holder and reporting capability would be coded and used for subsequent code generation. This approach allows for uniformity of the source code and its associated documentation.
The family id prefix would identify the overall ID of the targeted source code. Possible naming conventions could contain system id, table name combinations as well as other identifying naming schemes. The overall desired effect is to allow the technician to know which component they are using by just a glance at its name.