Report SQL generated with Table Owner name

rbuser

How do I stop ReportBuilder generating SQL with table owner name
information?
We are migrating reports stored in one database to another database, where
the table owner name is different, and we get the following error -

" TdaMetaData.GetFieldsFromDataSet: Unable to open dataset:
OMNIX.NIM_SEC_PROFILES "

(OMNIX is the table owner name from database that the report records were
migrated from, so the SQL is invalid on the new database)

Thanks,

Mike

digitalmetaphors

Are you using the data dictionary? When you are using the data dictionary,
if the DataDictionary.UseTableOwnerName property is set to true, then the
table owner name is stored with the table name as an entry in the dictonary.
The cache is trying to find this owner.tablename in the data dictionary
database table for the table names. Try setting it to false and change the
data dictionary database table entries to not include the owner names.

Otherwise, if you aren't using the data dictionary, then the table names are
retrieved from the database by firing a query on it to get this information.
What database are you using and how are you connecting to it?

Cheers,

Jim Bennett
Digital Metaphors

rbuser

I`m using the Data Dictionary and UseTableOwnerName is set to False.
The strange thing is looking at the report template SQL, only one of the
tables (out of a few) has the owner name specified.
I`m wandering if this could be related to another intermittent problem we
see - where the Data Dictionary sometimes shows the real table names (and
owners I believe) when creating a report datamodule, instead of the data
dictionary aliased names. Could this result in the data dictionary updating
the report template SQL incorrectly using owner details for some (not all!)
of the tables ?

Using Oracle and DOA.

Thanks,
Mike

digitalmetaphors

It sounds as if the data dictionary has owner names defined in it for some
of the table entries. Can you examine the data dictionary data to find out
if the table owner names are stored with some, none or all of the data
dictionary entries? In Oracle, usually you will want UseTableOwnerNames set
to true. Try creating a new data dictionary to test and generate the data
dictionary entries with UseTableOwnerNames set to true to see if the problem
goes away.


Cheers,

Jim Bennett
Digital Metaphors