Is my Crystal possesed?

[WTKnow]

I want to know if it ever happened to anyone here?

I am using formula in all of my 40 reports that is :
_______________________________________________________
Local StringVar inString := {table.fieldNO};
Local NumberVar strLen := Length (inString);
Local NumberVar i := 1;

While i <= strLen and inString = "0" Do
(i := i + 1;
inString[i to strLen]
________________________________________________________

I have one Report that is working fine and i needed to create spin off of this one with different fields and sorting etc.
When I ran it I got a message that there is a problem in my formula. This was a copy of working well report with modifications.
When I opened Report to chack what happened - I saw some of my fields in Detail are moved themselves into different positions.
Test Grand Total for {Name}:
got changed itself to
Test Grand Total for {Company}:

I had seen it happened before and I had totally re-created Report from blank...but now I have less time for that and want to ask you if there is way to prevent it from happening. And HOW in a world that Grand Total changed?

Thanks,
TIA

 

[GJParker]

There is absolutley no way that a report would change the name of a field. you MUST be looking at a diffrent report.

Gary Parker
MIS Data Analyst
Manchester, England

 

[lbass]

If you accidentally dragged a grand total of a particular field from the report footer into a group footer, it would change to show the group total for the same field, but at the group level.

What was the error message on your formula?

-LB

 

[mocgp]

There is a possibility that Crystal is seeing the "InStr" portion of your variable name "InString" and attempting to process that as the Instr Crystal function. I think I remember having a similar problem where one of my variable names contained the characters of a Crystal function. I'm not suggesting that re-naming the variable will solve the entire problem, but I think I would do it anyway just to eliminate other potential issues.

 

[WTKnow]

I am using the same formula on EVERy one and each of my Reports. InStr never confused any Report before (well, once only). But out of about 40?
I am very surprised i am the only one who gets this.
I am making few copies of the Report marking 1,2,3 and run them one at the time. Opening up - all fields messed up, deleting. Running #2...same thing.
Then I opened blank and got fields back re-positioned and nice. Ran - scrumbbled again.

Please, believe me it is happening. But I can not believe it is happening to one single Report writer. Ever on Earth!
LOL

 

[lbass]

Again, what was the error message on your formula?

-LB

 

[WTKnow]

I can not re-create message anymore. It displayed field {table.fieldNO} and said something like 'There is an error in {table.fieldNO}' BUT it said it in third party software I implemented it into.
When I run it outside of that package it gives me no messages but fields are changing places.
Like I said field with formula stays put.
Few other fields like CusName and RepName gets swithed so
from positions CusName (1) and RepName (4) - CusName goes to the end pos 9 and rest of the fields get shifted tot he right (because CusName moved tot he end) and weirdert thing that
Test Grand Total for {RepName}:
gettingt changed itself to
Test Grand Total for {CusName}:

Please, do not waste your time on this - just let me know if anybody had met this problem before.

 

[Dimst]

WTKnow,

A simular (not extreme like yours though) effect has happened within our reports.

Are the reports originally made in an older version of crystal reports and later converted to a newer version of crystal reports?

When i converted my reports from crystal reports 7 to crystal reports 8 all the record selection formula's from the subreports where gone! (at the time, no servicepack was available, nowadays i don't have the problem any more)

My theory is that when opening a report in a thirdparty application, crystal reports uses the configuration of that application and that overrules the crystal reports configuration. This can also happen when having the ODBC driver configuration set to a specific portnumber. then using in the thirdparty application the original report and viewing it. When looking at the odbc configuration the specific portnumber was changed.

(also; nowadays this problem is not happening, because in the meantime we have installed some servicepacks for crystal reports and the other components)

Hope it is helpful (however, i doubt it of course....)
-D

 

[pelajhia]

fyi, if you are using the same formula in 40+ reports, you might want to add it to the repository so you can make a change to it across all reports at one time...

I have never see anything like this occur however your statement "BUT it said it in third party software I implemented it into."
makes me curious. Where are you running the report when it's all messed up? Crystal Designer? Business Objects? 3rd party software?