Re: where to put a procedure so all forms can get it

[Quoted] So ... what's the better way of sharing front-end PL/SQL, attaching a library (per Alan) or inheriting from a master form (per Daniel)?

Does the inheritance method only work with Forms, not Reports? (I remember it wasn't possible in Reports 2.5)

Possible discussion points:
* ease of building, testing and sharing
* sharing code between Forms and Reports (obviously has to avoid using product-specific built-ins)
* effort needed when shared code needs to change * runtime performance

Martin

Daniel Morgan wrote:

>Timbo wrote:
>
>
>
>>I created a procedure (using hints from a book) that allows the forms
>>window to be closed by clicking on the "X" box in the upper right
>>corner to follow windows conventions. The book didn't indicate where
>>to build or place this procedure, so I put it under the "Program Units"
>>section in Object Navigator. It works and I can use it with a trigger
>>in the form.
>>
>>My questions are:
>>
>>Is this the best/proper place to put a procedure?
>>
>>Where would I put something so all forms could access it?
>>
>>Based on answer(s) to above, how would I access it from other forms?
>>
>>Using forms developer 9i. Developing on pc running OC4J, but
>>the app will eventually run on 9iAS R2
>>
>>The book, by the way, is "Oracle Developer Forms Techniques" by
>>Bulusu Lakshman, which has a lot of how-to stuff, but assumes the
>>reader already knows forms, which I don't. Not the best book for a
>>novice I have discovered!
>>
>>Thanks,
>>
>>Tim
>>
>>
>
>Does the procedure reference front-end objects or back-end objects? If
>back-end then just put it into the database and keep your front-end lean.
>
>Any code that can be put in the back-end is going to be better than
>duplicating code in the front-end.
>
>If you must put it into the front-end ... then put it into a master form
>and inherit it into your application so that you only have to maintain it
>in one place.
>
>Daniel Morgan
>
>
>
Received on Wed Oct 23 2002 - 03:12:16 CEST