Remove Schema From Table Name

[peggys]

I am trying to write reports against a database schema CISNEW. I want to deploy this report to a user with a schema CIS12345. Currently, when I try to run this report at the client site, it bombs because it can not find the CISNEW schema. How can I eliminate the schema name from the tables so this report will run at any client?

Peggy

 

[pgtek]

hi
check this link

http://support.crystaldecisions.com...indexq2=&indexq3=&indexq4=&btnG.x=28&btnG.y=3

cheers

pgtek

 

[peggys]

Thanks, I'll try that.

Peggy

 

[pgtek]

hi read this

The ODBC DSN was created using one set of logon
information.

You are attempting to connect with another set
of logon information.

The ODBC data source name (DSN) connects with
the CR Oracle ODBC drivers.

The original logon information has
administrative rights to the database schema.

The second set of logon information have the
same rights, except the ability to assign rights.

Both of the user names and passwords have
adequate rights to access the stored procedure.


How do you connect to the stored procedure
using a different user name and password or logon
information?

Why is the stored procedure missing or not visible?

Solution

To connect to the stored procedure using different
logon information, configure the ODBC DSN that you
are using to connect to the Oracle database by
clearing the 'Use current schema for
SQLProcedures' check box. Change the ODBC DSN in
the ODBC Administrator.

This enables the current logon information with
the adequate rights to display all the stored
procedures from different schemas.


Background
-----------

The stored procedure is missing or not visible
because Crystal Reports displays stored procedures
only from the current database schema based on the
current logon information. Based on how the ODBC
DSN had been configured, Crystal Reports does not
display stored procedures that belong to another
database schema.

cheers

pgtek