Making PLL library code amendments effective in Reports 10G

Question

What is necessary to cause a change to a PLL library program unit that is shared by many reports effective in all the reports?
I have read:
*[http://www.tek-tips.com/viewthread.cfm?qid=1021116&page=13|http://www.tek-tips.com/viewthread.cfm?qid=1021116&page=13] +"to make changes available you need not only to save the changes, but to delete and reattach it in the Attached Libraries node."*
Is this correct?
If so, doesn't this make PLLs pretty useless for Reports common code ?
I am using Reports 10G.
Jonathan

Answer 1

You can have just pll files in the directory, but Reports has to compile the library every time you use it. Therefore it is better to deploy plx files.
When you deploy at a customers site, it is always better to give them the plx files, since they cannot change the code that way.
If you get an error message deploying the plx, it probably means that the database where you developed your pll and the database where you deploy the plx are not the same. See if there are any differences (in table structure, stored procedures etc.). Maybe you have hardcoded schema owner or something in you pll.