Phantom components -- can't delete them! 2

[baisa]

using v4.1

Many times I will delete a component on the report, but somehow a phantom version of it stays inside the report somehow. Actuate tries to generate code for these phantoms, and if there are any bad references, then I get errors and can't build my report! There is no way I can find to completely delete these. Even when there are no errors, you can still see all the code being generated in the .bas file from the phantoms.

Anyone else had this problem? What can I do (short of completely creating a new report from scratch.)

Brad Aisa

 

[actuate5]

Hi Brad, please see my response in parenthesis.
Many times I will delete a component on the report, but somehow a phantom version of it stays inside the report
somehow.
[If you click on I View---->Project Variables you will find those phantom objects that you had deleted earlier. They will appear like purple dice. You will have to delete from there.]
This feature of Actuate is not usual but I have not found any other preventive workaround for this yet.

Hope this helps.