Re: Attachable Library Changes Need Form Regenerates?

From: Lewis Cunningham <lewisc_at_rocketmail.com>
Date: 1997/09/22
Message-ID: <6062ht$k61$1_at_news.ycc.yale.edu>#1/1


 I belive if you add a procedure or function that comes above (in the list) any existing procedure of function, you need to regen. Also, if you change a package spec.

Lewis

Dan Townsend wrote in article <34267EB4.1144_at_ebmud.com>...

>Good morning, folks.
>
>I have just learned the hard way that a change to an attachable library
>in Dev2k may make it necessary to regenerate the forms that use the
>library. I added a procedure to a package in a library, moved the
>library to production, and most of the forms that used it GPF'd all over
>themselves. Regenerating the FMXs resolved the problem.
>
>I had thought that attachable libraries could be changed and implemented
>without having to regenerate the forms, and up until now that had been
>our experience. But at least in this case that is not true. My question
>is this:
>
>Can anyone tell me what kind of changes to an attachable library will
>cause us to have to regenerate our FMXs?
>
>TIA.
>--
>Dan Townsend, Enterprise Database Architect
>East Bay Municipal Utility District
>375 Eleventh Street, Oakland, CA 94607-4240
>(510) 287-0272 mailto:townsend_at_ebmud.com
Received on Mon Sep 22 1997 - 00:00:00 CEST

Original text of this message