Hi folks -- My thanks to all four of you for your responses. I found them particularly interesting to read together, in that it seems like they represent alternate ways of looking at the same problem. Some seem to start with the objects, and some with the databse fields. I admit my knowledge of both databases and OOP are somewhat elementary (I've never needed DB's beyond "MyBase" style ClientDataSets, for example). I find data aware controls simplify programming (an advantage), while simultaneously encouraging me to program by writing a whole bunch of event handler code in Form1, rather than breaking my work up into logical classes (a disadvantage when I come back months later and want to change the program). So, as a way to teach myself to be more "OOP-ish" I'm working on rewriting some simple things I've done in the past. I tend to end up with the same problems when trying to divide everything into nice, neat classes--
--problems related to sending information between classes, --problems trying to decide where to put properties and methods relevant to two or more classes (e.g., employers have employees, and employees have an employer), and --problems related to saving information. I posted several times last summer related to the first issue, and got some great responses back that helped me. I think the second point I'll continue to learn about, but it's at least part of the art & decisions of object oriented programming ... and now I've got things to think about related to the third point! Thanks for your help, as always -- Al _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
