Andy,

>I just had a friendly conversation with one of the VB types here at work. I demoed one of my apps for him because he wanted to see the OOPS implementation in VFP. He was surpise to see how much of VFP was object oriented although he said it was still lacking some things to be completely consider to be OOP.

VFP fully supports the 3 things required for a language to be considered OO. Inheritance, Encapsulation and Polymorphism,

>Before he left, he suggested to me to create a customized object to hold all my procedures and functions. Ok, I thought about doing this when I first started on the app about 18 months ago but I didn't think it was that big of a deal. Was I wrong in thinking this?

IMO, If functions are considered to be language extensions, like an IsObject() function then it should be written as a function not a method. Why go through the overhead of method calls and worrying whether or not the function provider object has been instantiated so you can call it?