>> - I've seen too much procedural code ported to VFP (I've even been responsible for doing some of it) where rethinking the design to take advantage of the OOP environment woudl result in a better app.
>
>Hi Ed,
>There is also another reason for that. I've met many cases when the client wanted the app ported to VFP, but had not enough money (or a close deadline), which prevented the programmer from complete redesign and redoing it the right OOP way. Result is a camel-like app (OOP/procedural hybrid.) :) And it is not the programmer's fault.
>

I'm fortunate enough to not have the headache except where I made it for myself; most of my clients are concerned with the long-term aspects of their systems, and realize that if you do it cheap and wrong the first time, it's going to cost a whole lot more to then go back and fix it, and then have to go back and do the app over again the right way. And it's going to end up taking a lot more time to fix after the fact.