Search results for query: *

Create a formula field that contains your text. Use HTML formatting tags, as in &quot;This is a &quot; + &quot;<strong>&quot; + totext(variable A) + &quot;</strong>&quot; + &quot; licence. The licence has been defined utilising the &quot; + &quot;<strong>&quot; + totext(variable B) +...

When some people say they don't want rounding, they mean they want the precision of a number retained. Other people mean they want a number truncated at a certain point. Which is your preference? To ensure clarity for the simple minded like myself, please include an example.

You can't use this particular function with a input date parameter. You can use that single input date parameter to define your date range - this is slower to code, but the reports run faster this way.

Try this, just to tidy up your else statement: If {@newdate} > date(2000,01,01) then 1 else 0 ; If that doesn't work then @newdate is likely the problem. What does this formula contain?

Create another formula containing A/B, and leave it as numeric. Use this field to sort by, but don't display it on the report. Use the formula containing A/B converted to text as the field to display on the report.

A Report Option is to convert null values to default, which in this case would be zero. Sounds like you want to ensure this option is not selected, so that you get nulls returned in an unconverted state.

Darrick, You've posted something very similar in thread767-136403 a few days ago in this forum. It is probably quicker to use a single thread to solve a single problem in a single forum.

Sorry, that should be A right outer join B where A.id is null. Need to drink some more coffee...

A left outer join from A to B will give you records that DO have matching records, as well as those that don't. {b.id} will never be null in this result set A record selection of IsNull{a.id} would work, although it would be slower than using a where not exists... statement in a sp.

What database driver are you using? Have you considered using a stored procedure or view? This is the most robust way to pass more complex queries through to Crystal.

You may be using a function in a Crystal Reports formula that is version specific. For example, if you created the report in V8.x of Crystal, and Symposium uses the V7 engine. Try saving the report in V7 format (Save as...), and see if it will run then. Can you identify which formula generates...

Well, I never experienced this error, and am not able to duplicate it. I guess that this is fixed in version 8 and later. I wonder if this might only occur if you write an if-then-else statement without a closing else. Can anyone with V7 duplicate this, and see if it only occurs when the else...

Record Selection Formula: {LoginDateField} in (CurrentDate - 7) to CurrentDate

What happens when you try the following? 1) create a section, put the {LargeField} in it by itself, select Can Grow as a field format option. Test this - you should get see the formula, but not have the page breaks where you want, and the section will print even if nothing is in it. 2) Format...

This will give a substring from the field beginning to the first space. {fieldname}[1 to InStr({fieldname},' ')]

It doesn't show up in the formula editor. Put the field itself directly in the section. However, you can test for null for the &quot;large field&quot; in the formula editor. You just have to type the name of the field in the formula editor, using the standard syntax Not IsNull({table.fieldname})

> = should not have a space between - use >= instead. One of them should be <= also

Kelly, I misread that - Balves' suggestion is the simplest and is effective. If you wanted to do it within the SP, then you could add an extra field, but populate it with null values except for the first record. This might be a pain to do, depending on how your sp works. I did something very...

You can put this field in its own section, and format the section to suppress if blank.

Why not pass the ID description as a field in the stored procedure by putting it in the SELECT statement of your SP, and then place this ID description field in the report header? Each record then it will then contain the correct description for each ID field.