Oracle Forms

Hi,

I don't know if I'm the only one who've experienced it, but working with Attached Libraries (PLL files) is sensitive stuff. And that's NOT a good thing these days as putting things on production servers has to go through a lot of other people in the organization - so when I deliver something it HAS to work.

I'm wondering if there's any official strategy to working with the PLL files?

- How do you make sure Forms Builders doesn't "drop" the PLL (it's as if it's still recorded as being attached, but it just isn't in reality)? (I've sometimes tried to set Read Only on the PLL files to avoid this dropping of libraries, but I don't know if it makes any difference)

- How do you make sure the Form picks up changes to your PLL file? Is compile_all enough?

- When you've changed a PLL and needs to compile the FMBs, how do you do it? Do you compile the PLL and leave the PLX in your source dir, THEN compile the FMX (using compile_all=YES). Or do mustn't there be PLX files in the folder where you're compiling everything?

- And on a production 9iAS (windows platform) - do I deploy the PLL or the PLX, or both?

Regards,

Jesper Vad Kristensen