>Agreed. I stated "compiled" in my post.
Yes, right.
>Didn't know this. Still a pain in the arse to have to move all my code around, split up my create view blocks, etc. You would think it would depend on available memory, but I'm obvously not at a level to understand why the 64k limitation exists.
Looks like at some point, the 32-bit code which the compiler creates isn't 32-bit in every aspect.
It looks to me like an addressing problem. For example - and while I obviously don't know the internal workings of a VFP program - in a FOR...ENDFOR loop (or any other loop, for that matter), either at the ENDFOR or at the LOOP command, the compiler will likely mark the byte address of the FOR command (similar to a GOTO (linenumber) in BASIC), so that it doesn't have to search where to go to, in every repetition of the loop. Now, if this "jump-to-address" is stored as a 2-byte number (16 bits), that would limit the size of the particular procedure to 2^16 bytes.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
