>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.
>
>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?
Keep in mind also that methods and events cannot contain nested procedures or class definitions - they have to be in PRGs. Also procedures in separate prgs may be more convenient for debugging purposes. Say, if you test the form or report which call some procedures in this case you do not need to instantiate your procedure object.
Nick
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro
"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison