Michel,

It's not the object that is too big, but one of the methods. One of your methods has gotten larger than 64K (after compiling) and needs to be broken into two or more methods to fix it. The limitation is per function/procedure (which for that purpose is what a method is). Find your largest method and break it into at least two parts.



>>"The program that Visual FoxPro is attempting to load will not fit into memory. The largest program or individual procedure Visual FoxPro can load is one containing 65,000 bytes."
>>
>>I think you´ll need to refactory your object. And what a huge object, huh. :)
>
>This is a nightware. I've been working on that object since a year now just to find out that it has to fit within a specific size.
>
>And, believe me, it's not a bad design. It is fairly simple. It's just that it does a lot.
>
>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?