I've been away for a few days with those pesky real-life things, but now I'm back ... Since several of you have been helping me, let me tell you that I completed a small exercise I created for myself to apply the kinds of things y'all have been "teaching" me. It's nothing more than a simple database that lets me keep track of the status of applicants to a graduate school program I coordinate--nothing I haven't been doing with the simplest of spreadsheets.
Still, I'm pleased with the results and want to thank you all again. There's four classes--the GUI, TApplicant, TAppList (wraps TList, keeps list of TApplicant instances), and a class derived from TAppList that adds functionality for saving and loading info to/from a CSV file. Normally I would have just written event handlers in the GUI class. Four classes instead of one is more complex, but I can see the advantages. I think the various classes are easier to understand than one long class, and I think it would be easier for me to change the user interface or file format with the multi-class arrangement than with one long class. Thanks again -- Al _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
