>
>And, believe me, it's not a bad design. It is fairly simple. It's just that it does a lot.
A object can´t do a lot, it can do only a thing. ;-D
>
>Now, the program is at 177k. Why is VFP only starting to complain? If the help says 65k, I bypassed that limit a year ago.
>
>Now, what about refactoring. How would I go about this to solve this situation by keeping one and only one object where all its properties and methods will remain as is?
You can use delegation or implement the bridge pattern, as Claudio say.
You can create a interface class with all your original property and methods, and some classes to do the things. You can create the no-interface class in at Init() Method and asign this object to new properties. In your original methodes you call to the object has the method with all the properties that it change.
It isn't easy work, but a solution.
Regards,
José Luis.
Quidquid latine dictum sit, altum sonatur