Jim: I was by no means antagonized. I like a good argument as much as the next guy (maybe more). I was just trying to make the point, with probably a bad example, that a well-thought out OOP system *should be* easier to maintain than a procedural one. Much is dependent on the skills of the developer; a good VB developer can whoop up on a bad VFP developer and vice-versa.
Any change in an OOP system that incorporates subclassing based on app standards, wrapper classes to encapsulate external calls, business classes to encapsulate business logic, and -- maybe -- IO classes to wrapper/isolate table calls *should* be easier to maintain and modify for whatever reason.
Sorry if I misinterpreted the tone ;-D
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05