>>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.

Yes, this has been pretty much the same message since 1.x and IIRC has always meant the same thing. In 2.x it could be particularly troubling since you could build a large screen using genscrnx and something like the tabs driver and 3d driver and get the main part of the spr file too large. This also is common with gendbc with larger dbc's which is one of the things gendbcx fixes by putting each tables rebuild code into a procedure call.