Forms without the dfm is a virtuous pursuit. In addition to eliminating the dfm many of the event handlers are also able to be consolidated. This level of concision allows for low overhead and very tight coding. There generally are a limited number of patterns involved with many information technology problems. This application allows the technician to identify, isolate and store these patterns.
The main functions are “Load From File”, “Clone New Unit” and “Export Code”. There are two report features “Basic Report” and “Design Report”.
When the user selects the Load From File option the following dialog appears.
The applications determines if the file already exists in the database and if it does exist it is not overwritten. If the file does not already exist in the database it will be added and will be avaliable in the repository.
When the user selects the Clone New Unit option the following dialog appears. Notice the dialog is populated with the name of the field that was selected prior to clicking on this option.
You must change the member name to a unique name before cloning takes place. When cloned the appropriate names are changed dynamically.
When the user selects the Export Code option the following dialog appears and the user is prompted to select the target directory.
The frm001 file is searched for and if it is not in the target directory it will dynamically be copied there. If the file already exists in the target directory no further action is taken.
When the basic report option is selected the following report preview appears.
The Report Designer comes active if the version of Fast Reports supports the designer. At any rate the forms with no DFM are fully functional.
The database is description and data is stored in the file “frm.sql” in the source code directory.
A 32 bit executable program may be downloaded by clicking here.
A 64 bit executable program may be downloaded by clicking here.
The component documentation can be found by clicking here.
The source code may be found by clicking here.
Mr. Arch Brooks, Software Engineer, Brooks Computing Systems, LLC authored this article.