> But > Isn't it more a matter of philosophy how to solve a problem? Aren't there many different ways to write a program to do a job? > So each of the discussed solutions has its own benefits and its own (sorry I do not know what the opposite of 'benefit' is) pitfalls. > > If you want to find out the best solution, you'll fail - wrong question. > > If you want to find the best FOR YOU (for your Customer). you'll have to make up a list of goodies and worsies of every solution and then - decide!
You are quite right, and that's my point. It's a matter of taste. It is common for people to become familiar with one tool and like it so much that they start to use it in situations where another approach would be better. A common example is the widespread use of shreadsheets as databases. If the only tool you have is a hammer, every problem you see looks like a nail. Glenn Lawler ----------------------------------------------------- Home page: http://groups.yahoo.com/group/delphi-en/ To unsubscribe: [EMAIL PROTECTED] Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/delphi-en/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
