Compiler crash Forms 6i

Question

Hi,
I have a problem with Forms developer 6i. I have a very big form 2.3 MB, and then I added some extra lines of code ( and there are no errors in them ), and when I try to recompile the fmb now it crashes the whole forms developer program !
I think I hit maximum compilesize for fmb's or something - but then again can that really be true ?
Have anyone experienced similar problems ? and does a solution exist.
PS - I tried to add the lines again from the functioning fmb and same thing happened again and again at roughly the same point - around 2.3 MB
Kind regards
Bo Normann

Answer 1

First of all, the last two posts are implying that the runform session is crashing. Please note that the original post is talking about the Forms Builder crashing.
I couldn't understand the logic behind 'Finding and Replacing' a semicolon with a semicolon through out the form.If you compile a form, you will notice in the Object Navigator, that each program unit has a '+' by them that you can click and see more options. If you open the source of the program unit, at the bottom of the editor window it says Not Modified . . . Sucessfully Compiled. If you save the form, close it, and re-open it, the program unit still has this compiled indicator.
If you change anything in the program editor, the compiled indicator disappears. If you save the form without compiling, and reopen it, it is still NOT compiled.
All you are doing by changing semicolon to semicolon is forcing every trigger and procedure to become uncompiled. And then if you save the form in this state and check the fmb size, you will notice a much smaller fmb size. You will notice when you open such a form in the Builder, the open is faster, and the first compile is slower (just like doing a shift-ctrl-K compile-all). On the other hand, a form saved with all compiled code opens slower, but first compile is fast. Apparently when Oracle opens a pre-compiled fmb, it tries to verify the compiled program units.
However, these compiled program units cause problems -- we have had problems using pre-compiled fmb's transported to different environments failing in stored-procedure calls and other places. Doing a compile-all (shift-ctrl-K) clears the problem.
The bottom line is this: Storing compiled code inside an fmb does no good. Oracle has been doing it from the beginning of client/server forms, along with storing a copy of the color palette, too. In BOTH situations, this has caused issues with forms, especially when moved from one environment to another. In my workplace, we make SURE we always store production forms WITHOUT the compiled code. They transport quicker due to smaller file size, and they compile cleaner in the users environments.