PS: Cheers, Ken - been reading you for something like 7 years now!

Thanks for the contribution. If you follow the link to my original formula you will see that the main formula is designed to work with a ‘reset’ formula, which is why there appears to be a dead variable. The ‘reset’ formula prevents the initial comma and also allows a separate accumulation for each group. This is described in the original formula page but probably not very clear here.

So I tested my version of this formula with a grouped report and found that the ‘reset’ formula needs to be changed for this expanded formula. It should also reset the variable ‘SetCnt’ back to the number 1 at the beginning of each group.

Your version does work better if there is no need to have a group reset.

Thanks very much for all that you do in putting this Crystal information out there.

In this blog entry the code from Shelly generally works, but includes dead code and dead variables. Note that the variable ChCnt is only set to the value of 2 (other than 0 initially), but is tested for a value of 1.

Below I have eliminated the dead code and variable plus I added a simple test that eliminates the comma from the beginning of the resulting composite string.

WhilePrintingRecords;
StringVar Item:= {your.stringfield};
StringVar Chain;
NumberVar ChCnt;
NumberVar SetCnt;
StringVar Set1;
StringVar Set2;
StringVar Set3;
StringVar Set4;
StringVar Set5;

if Length(Chain) + Length(Item) > 200
then (SetCnt := SetCnt + 1;
if SetCnt =1 then Set1 := Chain;
if SetCnt =2 then Set2 := Chain;
if SetCnt =3 then Set3 := Chain;
if SetCnt =4 then Set4 := Chain;
if SetCnt =5 then Set5 := Chain;
StringVar chain := ', ' & Item)
else if chain = ""
then chain := Item
else chain := chain + ', ' + Item;
Setcnt & ' ' & Chain

Regards,
Dan

Note that ESD is only used to distribute service packs to products like BusinessObjects Enterprise and the midmarket Edge product.

Service packs and fix packs to Crystal Reports are publicly available to all licensed users (not just customers that pay maintenance), so they are publically accessible and do not use the ESD system.

We are aware of the recent issues with ESD and are looking into it, but these do not affect how Crystal Reports customers get their service packs.

Thanks, Blair

There are 2 potential workarounds:
1) Create an environment variable called “CRUFLPATH” and the Crystal Reports 2008 installation location of u2lcom.dll to this variable. For example in a default installation this would be:
C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86

OR

2) Remove the u2lcom.dll from Windows\System32 or Windows\Crystal

This is expected to be fixed in the first service pack to Crystal Reports 2008 that is planned for late Q1 2008.

Thanks, Blair

He has also released Mass Verify 3.0 which now includes support for ALL of Crystal Reports data sources in one tool. It also adds the ability to save database connection settings to a profile so that so you don’t have to re-type them each time.