Guest.Visitor
12-25-2002, 01:08 PM
Hello Robert I agree with nearly all of what you said about the above and I have a few additions: 1. Component builders, since they have to write to a general audience, have to cram the product with stuff you don't need - this leads to bloat and its attendant problems - in-house built just does what you want with all the felxibility to add anything else you may want in the future. 2. If you buy a component you may be able to buy in other add-ons but it's not guarenteed - if you write them YOU decide the direction of future development without having to hope that some else does it for you. 3. The writing and maintaining of components is great programming practice and is best kept in-house. So to end I would say it's horses-for-courses - but I lean towards in-house due to my experience of the quality of utilities, written commercially, that I have seen during my career. Best Regards Mike