Crystal Reports - Converting Custom Reports 1

[DavesWorld]

Hi all,

I have a question for you Crystal Reports gurus out there. I'm trying to make the process of
converting custom reports from 8.5 to 10.0 a bit more efficient.

I have one method that works for fields in the group sections, but not in the detail section.

For the fields within the group sections, I right-click on the group, click on "change group" and
then reassign the new field name without having to change anything in the group structure.

I'm wondering if it's possible to do something similar in the detail section. I'm trying to avoid having to recreate the properties the original field had in Crystal, such as borders, sizing, fonts, etc.

Here's what I've tried for the detail section: I right-clicked on a field to be changed, clicked on "select expert", deleted the old name, clicked on "new", and added the new field name. I clicked OK, but the change didn't take. (One thing I didn't try was adding a formula in the editor to see if that would make the change take hold, then delete the formula).

Just wanted to mention that when I start upgrading an 8.5 report, I create another connection under Database Expert. This way, Field Explorer contains both old and new tables.

Hope this made sense.

Thanks in advance for any ideas.

 

[dgillz]

Don't add the new data source, just change the data source location. You will be prompted to go through as field to field mapping process if the existing field names do not exist in the new data source.

Not sure about crystal 10, but in 8.5 and older, there could be one ugly thing to deal with - the "old" table names will still show up in the database expert. If this is an issue, set an alias as the table to the new table name.

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

"If you have a big enough dictionary, just about everything is a word"
--Dave Barry

 

[BigLouie]

Dave why not just use the report conversion wizard? Why make it so hard.

 

[DavesWorld]

Big Louie, dgillz:

Thanks for the input. I should have mentioned that the reports I'm converting contain SO1 and SO2 tables.

I was told by several people that the Report Conversion
Wizard doesn't work well with the new modules. Is that true?

I see what dgillz is talking about. I thought it was something I was doing wrong when the fields displayed on the form as OldTableName.NewFieldName.

 

[DavesWorld]

Big Louie,

I think I just answered my own question. I just ran the Report Conv. Wizard. The first time, it got hung up on a UDF table. I thought it might still change the others.
I looked at the report, no change.

I decided to remove the UDF tables from the report first. Once I did that, everything converted perfectly -- formulas and all!

 

[BigLouie]

Ya see, nuttin' to it

 

[dgillz]

Just so I understand in the future, I take it this wizard is a Sage tool?

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

"If you have a big enough dictionary, just about everything is a word"
--Dave Barry

 

[DavesWorld]

Yes, I believe it automatically gets installed with MAS. The name of the executable is MASCRCW.exe

It's located in the "Home" folder. Your path will be slightly different, but here's an example:

S:\Sage410\MAS 200\Version4\MAS90\Home

I'm not sure if it's intended to be launched within MAS,
but I ran it right from the Home folder.

 

[BigLouie]

Yes it is a Sage tool and it is in the MAS90/Home folder. When you attempt to run a report on the Custom Reports menu it will kick off but you can also run it outside of MAS if you want to update a whole folder full of reports.

Note that you must use a THREE (3) digit at least log in. A two digit login will cause the wizard to fail.

 

[DavesWorld]

Re the tip that dgillz sent about adding the table alias when you're changing the datasource location -- dgillz, if you're out there, can you tell me how to do that, or if anyone else out there is familiar with that.


Thanks!