<i><font color="#663300">Therefore by using a common luname, cid I have built classes for the entire functionality;
acifcombobox - subclass of iifcombobox
frmsystem - a listbox with the primary groupings - colour, breed etc... and the 2 character combocode whic calls frmlookup.
frmlookup - a form containing a list of all entries for a particular code - e.g. colour, provider etc..
frmcomboedit - to edit or add new entries for those records only requiring the base information - cid, luname including new items from acifcombobox.
other forms are subclassed from frmcomboedit using a container with the additional information.
The whole thing ties together into a complete lookup table maintenence system with minimal filling in of properties for different groups. In most cases all that is needed is to place the 2 character combocode - CO for colour, BR for breed and so on to get it all working.
Anyway, it almost complete and bug free. If there is interest I can write an article for the Wiki on the new app development manual. Is this the sort of thing needed for this project? Can I post screen shots on the Wiki or is a Word article posted through the download page better?</font></i>
I think the Wiki is the way to go. You can upload images to include in your Wiki pages; see <a href="http://fox.wikis.com/wc.dll?Wiki~WikiFTPDirectories~Wiki" target="_top">http://fox.wikis.com/wc.dll?Wiki~WikiFTPDirectories~Wiki</a> for instructions. And I'd be happy to post the files on the <a href="http://leafe.com/cb6dl.html" target="_top">Codebook download page</a>.
One thing I would suggest: don't hard-code your chosen field names. Make them class properties, such as "cLookupNameField", so that everyone can adapt these classes to their own naming convention.
<font color="#cc0000"> ___/
/
__/
/
____/</font>
Ed Leafe
©2001 Ed Leafe |
