>a cat a cat and acknowledge that VFP is not OO in the sense most authors

If you want "full" OOP, you try SMALLTALK or EIFFEL (I'd stick with the first). VFP is as OOP as C++ or any other in it's genre, that is: hybrid. It means you can do it either way.

OOP is more costly! Thats just a half true, let's see why:
1. OOP is the present and maybe the near future, wich means that if you stick with traditional, you will be risking loosing the train, and that means clients (wich are why we exist).

2. It will take more time to create new standards in terms of development (standard libraries, that is). But after you have them, all you have to do is to change what's necessary to that application. And that's fast isn't it?
For instance, as all my clients are portuguese, I had to create a new message box with the button caption in portuguese, It's called exactly the same way. It toke me some time (it was the first thing I did with VFP), but all I have to do now is call it. That's reusability.

Now, how much does the transition costs ?

Alex