Update Command

[bubu2006]

Hi,
I am using command in one report. Now I want to change the service name. Do I have to recreate the command in new service? I was trying to use same method which I use for view or stored procedure.

I am using Crystal report 10.5 and Oracle9i.

Thanks,
bb

 

[synapsevampire]

Service Name is a what?

A field, a table, or???

and what does "Do I have to recreate the command in new service?" mean?

I don't know of any new service functionality which controls any commands, if you mean a database connection named service then please so state.

If you want to edit a query within a command object, use Database->Database Expert-Selected Tables, right click the command object and select edit.

-k

 

[bubu2006]

DSN name. If you want to change the DSN name you can click on set data souece location and update the datasouece name. My question is if I create a command in one DSN can I update that to another DSN or I have to create new command under new DSN.

 

[synapsevampire]

DSN's don't embed Command objects, they define connectivity, and Command objects are SQL that is passed through DSNs.

You say change the dsn name, then you speak of creating a new dsn, these are not the same either.

Your dsn can be changed to point to the NEW datasource, and then the command (sql) will run aginst that data source.

Also keep in mind that there isn't a type of connectivity in Crystal called DSN. If you mean ODBC, that can use a DSN, as can an OLE DB connection.

And in some versions of Crystal there was a DSN builder under ADO/RDO which allowed for pasting SQL, but it was NOT a command object.

Try posting what it says under the database expert as the type of connectivity, and if you're using a DSN, you might consider that you are slowing Crystal down, you should be using the Oracle Native Connectivity as it's the fastest and doesn't require DSNs or ODBC.

-k

 

[Turkbear]

Hi,
To further expand on Synapse's excellent summary, a report using ONLY a command object can have its source 'pointed' anywhere that the structure of the data is identical..
That is, a report ( created by a Command Object only) accessing a test database instance ( determined by the login info supplied are runtime/publishing time) can be redirected to a production instance simply by logging into the new location instead of the old..( Again, if the data structures are identical)..

The command object, as has been mentioned, is just a Sql command that will be sent to whatever database instance the report is connect to..

If both a command object and 'standard' tables/views are in the report, the 'Set Location' options are only needed ( and can only be used) for the non-command object components.







To Paraphrase:"The Help you get is proportional to the Help you give.."