> If you are going to do that, you could make life easier for everyone if you > would make a small structural change to the form description in Sys_Forms3. > Instead of the EEP Code being inline with the Object that has the EEP, make a > reference to it and keep the Code (all Code) for the Form in a contiguous > place at the end of the Form Description
I already have an enhancement request in for a menu option in the Forms Editor to display a menu of all code snippets stored in the form (so you don't have to hunt for them all over). Mike's suggestion, however, is much superior to mine, and I would rather see that implemented. My only additional suggestion is that, instead of having that code stored in the form definition, put it in a separate column in sys_forms3 (called SYS_FORM_PROGRAM or something). Then reference that from the SYS_FORM_DATA column. This could be implemented through the same mechanism currently used to trace APX files -- since that mechanism is able to find and run a named piece of code from a collection of routines. I'm not sure that this is such a "small" structural change to the forms system, but it would certainly result in a quantum leap in the ease of editing code in forms, and make it easier to implement form code editing without having to actually open the form (which in turn will make it much easier, for instance, to find all instances of a given column name in embedded form code across all forms). -- Larry -- Larry
