SET ALIAS for Table Problem

[bjplayer]

I used Set Location to change a table name used in a report. This worked correctly. The old table name was mapped to the new table name, but the old table name still appears a lot of places in the report, including field names. I tried to use Set Alias to replace the old table names in the report with the new table name, but nothing happens.

In the Set Alias screen, the old table name appears highlighted under "Databases," and the new table name appears below it under "Location:" - "Table:new table name" When I click the Set Alias button on this screen, another "Set Alias" window appears with "Alias Name - Please select an Alias to refer to: new table name" Below this under "Alias Name:" is a text box with the old table name displayed. Since both new and old table names appear on this Set Alias screen, I just clicked OK, but nothing happened on the report.

Any ideas how to get the old table name replaced by the new table name everywhere in the report?

TIA.

 

[synapsevampire]

Save the report.

That usually does it.

-k

http://www.informeddatadecisions.com

kai@informeddatadecisions.com

 

[lyanch]

I have the same problem with a couple reports. For some reason the save doesn't work. Nor does a "save as". The only solution I have found for this is to create a new report using the correct datasource and copying all from one to the other. This is not by any means an easy solution as many things cannot be copied.

For an older version of Crystal (several years back) I had some code that would go in and fix all of this. I unfortunately no longer have access to that code and have not had this problem enough to need to recreate it.

Lisa

 

[bjplayer]

Boo. And Boo Hoo.

bjplayer

 

[synapsevampire]

Lisa: That's odd, I tried it here and I had the same condition, when I save the report, it fixes it.

<shrug>

-k

http://www.informeddatadecisions.com

kai@informeddatadecisions.com

 

[lyanch]

I agree, sometimes it just doesn't work. I have over the years found it more common for it not to work with very complex reports and/or reports using SP's. The one that I have that didn't change correctly now is from a SP. Because the name changed from SPNAME to SPNAME_TEMP until a database change/data fix goes in and then it will change back, I really didn't care.

If I ever figure out why some don't change... (yeah right)

Lisa

 

[synapsevampire]

Hmmm, I didn't try an SP because I can't use them at this contract.

<low gutteral growling>

I just set up a quick and dirty report, nothing complex..

Must be the difference.

-k

http://www.informeddatadecisions.com

kai@informeddatadecisions.com