When we created the new catalog we just made sure that if the table was named lawprod.employee and the fields were company, first, last etc... that in oracle it was lawora.employee company, first, last. Basically just make sure the naming conventions stay the same from one system to the other...
This is a piece of the code we use for a macro button. I am not sure if it what you are looking for but...hope it helps.
Set ImpRep=ImpApp.OpenReport("z:\biweekly\PT w vac sick pay.imr")
ImpRep.ExportExcel("z:\biweekly\PTw vac sick pay.xls")
ImpRep.CloseReport
It turns out that having the same table names (unique identifier) is exactly what did the trick. We can pull up old reports from sybase catalog and point them to the oracle catalog and 90% read them just fine. But you need to make sure old catalog is not still in the same place as new catalog...
Unfortunately the person who created the Impromptu catalog for Oracle has left our company. He did the converting of our Impromptu 6.0 reports to use the catalog but he didn't do them all now it is 2 weeks from go live and we have about 200 reports needing to convert and we don't know how. We...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.