I have a report where I am trying to keep track of the previous record's details. There are two fields I am keeping track of so that I can see if they are duplicated and ignore them, so basically my formula looks like this:
Global Field1 As String
Global Field2 As String
If {Table1.Field1} <> Field1 Or {Table1.Field2} <> Field2 Then
'do some processing
End If
Field1 = {Table1.Field1}
Field2 = {Table1.Field2}
I was noticing that from time to time that it wasn't catching duplicates...in other words, the test for a match was failing and it was processing the next record. I decided to just display what was in those global variables and sure enough, they weren't matching up. It almost seems like their values are random, too, coming from some other random part of the report.
Anyways, it's very odd...and not the easiest to explain, but maybe I offered enough to get some suggestions.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
>>This would ensure the formula is evaluated in the order the records are displayed (rather than in the order they are read from the database).
This sounds reasonable, however I have a running total based off of this formula, so when I make this change, I get the error "A running total cannot refer to a print time formula".
Right now the suppression of records using that NEXT/PREVIOUS method looks the most promising. I have made another version of the report going that route and have sent it off for the users to test.
Try adding
WhilePrintingRecords;
to the formula. You may have to use Crystal syntax to do this. Your formula will then be
WhilePrintingRecords;
Global StringVar Field1;
Global StringVar Field2;
If {Table1.Field1} <> Field1 Or {Table1.Field2} <> Field2 Then
(
'do some processing
)
Field1 := {Table1.Field1};
Field2 := {Table1.Field2};
mlmcc
Yes, that was the suggestion just prior to this one, and while I think it too could solve my problems, it seemed to have affected a running total I had based off of this formula. After adding the WhilePrintingRecords command, I then got the error " "A running total cannot refer to a print time formula". So, is there a workaround for that?
The PREVIOUS method was working in terms of suppression, but it all came back to the running total issue, as the formula, since its not calculating in the proper order, may show the wrong total since its calculating values that are being added to the running total, when in fact those values should be suppressed and not displayed nor considered in the running total.
So, what are my options? Basically, I guess what we are looking at is the following:
* I am suppressing data via the PREVIOUS keyword
* I have a formula that is calculating values for data that is not suppressed (supposed to be, anyways)
* In order to make the formula work properly, I must use the WhilePrintingRecords directive, but I then cannot base a running total off of that formula
So, how do I keep a running total internally? With another global variable? Do you simply use the Global keyword to share a variable across formulas?
Do you simply use the Global keyword to share a variable across formulas?
Yes. Although I have been told variables are global by default. You must declare the variable in each formula
Here is what I generally do
In the report header
Name - DeclVars
Formula
Global NumberVar MyTotal := 0;
In the detail section
Name - CalcTotal
Formula
Global NumberVar MyTotal;
MyTotal := MyTotal + {YourDataField};
""
In the report footer
Name - DispTotal
Formula
Global NumberVar MyTotal;
MyTotal
I believe formulas in suppressed sections are not calculated so that may work without having to redo the tests.
mlmcc
Well, I created a "shared" variable that was calculated using the adjusted formula with the WhilePrintingRecords directive, and continued to use the PREVIOUS keyword for suppression, and then used the "shared" variable running total instead of a "true" CR running total object. Right now it looks good, but I'm going to let it loose on the users to be sure and I'll come back and close this question.
Business Accounts
Answer for Membership
by: frodomanPosted on 2006-07-05 at 13:21:22ID: 17046082
Where in the report is this formula? Are there other formulas in your report that use these same global variables for anything?