Search results for query: *

Marta - For what it is worth I am having the same problem. Based on the Business Objects (BO) web site this is an ongoing problem for Crystal 7.0 - 8.5. There are some specific patches to download. I have just found this problem today and have to go through my IT department before accessing...

LB - That works! May all of your children receive full scholarships to Harvard. Many thanks, my day just got a whole lot better. - Kevin

LB - Again thanks for the response. I think I need to clarify my goal. We must report on all calls that are closed within a given work week, the period of closure not to exceed 2 days from the end of the reporting week. Thus I am using the Recv Date as a group with the "for each week" option and...

LB - Thanks for your reply. The @Recv Date & @Closed Date are as follows: @recv date: dtstodatetime({CallLog.RecvdDate}) @closed date: if trim({CallLog.ClosedDate}) <> "" then dtstodatetime({CallLog.ClosedDate}) else date(0000,00,00) I don't think these are the issue. The reason I say this is...

I am using version 8.5. I am trying to create a formula that indicates if a record was closed in <= 9 days after the beginning of the group week date. I am using a group based on received date with the "for each week" option selected. The formula simply establishes a value of 1 if the closed...

Mike - Simplicity is a virtue. Worked like a charm, also helped me understand better how the the DayOfWeek is being manipulated. If I could give you a raise I would - Thanks KP

Brian - Thanks for the response. That link is where I got the formula originally - I need help to modify it to result in a Thursday rather than Friday start date. Thanks - Kevin

We use an odd work week and I need to create reports based on the Thursday - Wed schedule. I am using 8.5 and am trying to modify the following formula to break on Thursday rather than Friday as it does currently (this formula was from the Business Objects support site). My dyslexic brain keeps...

I appreciate all of the input. In summary there are 2 ways to handle this, each requiring 2 steps: Method 1 a. Create a formula that converts the null values to blanks and use in place of the actual field: Ex. Formula name = Conversion Formula 1 if isnull({Table.field})...

In response to Ngolem: &quot;The user is &quot;ONLY&quot; grabbing records for a particular field that is NULL???? the Non-null fields are not selected. So what is the need for a field of this record with conditional colors on the background?? {shrug}&quot; I am selecting from records with 30...

The easiest solution is that from Ibass. This way I'm not writing 2 formulas (i.e. one to convert the null values to blank and one to interpert those within the background formula). Thanks for everyones help. Turns out the suggestion was avaiable on the Crystal Decisions web site as well...

Reply to Madawc: Thanks for the reply. Your suggested formula is the same as my current work around formula. I'm trying to avoid this step. When you say &quot;Crystal assumes that anything with Null is not wanted&quot; this does not make sense to me in the sense that my report selection...

I am using Crystal 8.5. I can make use of isnull logic successfully within the selection criteria but use of isnull reference to the same field within the borders & colors/background does not return the expected result. In selection criteria: isnull(Table.Field) - This returns only records...