>>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.
>
>Yes, as confirmed by several others. IAC, the message is not intuitive as it makes references to the program and doesn't mention anything about function/procedure.

Should be worth mentioning in the new 'Documentation' topic.