Re-map table usage in Oracle9i Designer

Question

Hi,
I have Web application in Designer. One of the module components has a table usage that is based on a view. After some initial testing, we determined that the view was not going to be fast enough for the application. We created a materialized view which solved our speed issue. However, our module component table usage is still referencing the original view. I tried to "copy object" on the module, which from what I've read allows the re-mapping of table usages. However, my client crashes when I click the remap button.
I'm using Oracle9i Designer 9.0.4.4.8.
Does anyone have any ideas, or possibly another way of accomplishing this task?
Thanks,
Chad

Answer 1

I'm trying to understand what you have and what you are trying to do. First of all, the Web PL/SQL generator requires you to generate Table APIs (TAPIs) for every table referenced in a module component. If you created one based on a view, the only way to get it to work is to generate a TAPI on the view, which Designer doesn't do natively. I've fooled Designer into generating a view TAPI by creating a table definition that looks exactly like the view and has the same name, and generating the TAPI for that table. Even then, I have to hand-modify the resulting TAPI to remove references to ROWID, since views don't have rowids.
I've never tried generating TAPI against a materialized view (MV) - it might work, since there really is a table to instantiate the MV, but it might require the same work around as the view.
As for the reference in the module component definition, I think you have to delete the old table reference and create a new one. I'm not sure what you are doing with "copy object". Remapping is usually done when you are copying an object from one application system to another, and want the references to point at equivalent objects in the new application system, not the objects in the old one.