Search results for query: *

Found the solution, for those who are interested: Clients were running Crystal Reports XI (original release) whilst server is running BOXI R2. Upgrading clients to CRXI R2 sorted out the problem: LOVs are visible in the query panel when creating Crystal reports.

Hi guys I'm having a problem building Crystal Reports on top of a BOXI R2 Universe. I need the List of Values (LOV) for a particular object to appear in the query panel when creating the query to feed to the report. For example, if I want to create a filter on "Helpdesk Name", then I should...

Have you tried simply formatting your data in columns? Open up the section expert, go to "details" and select the "format with multiple columns" option.

Hmm. Have you guys tried making sure that you have no saved data with the report?

OK, found a KB article on how to do this. You simply have to save the command object to the repository first. Full instructions here: http://support.businessobjects.com/library/kbase/articles/c2012566.asp I would still rather use views or stored procs, if possible.

Hi Alettia Just tried to do this myself, and I can't seem to get it to work. Perhaps one of the other chaps here can help. However, since you're working on SQL server, why not rather use views or stored procedures to base your reports on?

I have used Data-Direct (formally Merant) ODBC drivers for Progress databases running on a UNIX system. Their software works extremely well and they seem to be generally highly regarded as a source of useful DB bits and pieces. Their drivers are often bundled with various applications...

Your first formula should work just fine, although you may want to incorporate dgillz's idea of converting your strings to uppercase, just to be safe. This sort of problem usually occurs because your IF statement conditions are not correct, although I can't see anything wrong with this simple...

Not sure I understand. It sounds like you are not grouping on these date and time fields, so could you provide a little more detail on what your groups and detail looks like? It sounds to me like a simple record sort would work just fine. Have you tried using that?

lbass, Ah, right you are. It's all a blur, really. :D Neat solution with the SQL expressions.

If "sold to " is always the leader you can use the following formula: //some variables to keep the formula readable local numbervar nSpaceIndex; local numbervar nCommaIndex; local numbervar nIndexToUse; //find the first spaces or commas, after the "sold to " bit nSpaceIndex := instr(9...

Don't add the {@LateJob} formula to the columns in the cross-tab expert, but to the summarised fields section. You will also need to add the ActualTime field to the summarised field section. Then you'll need to place the "job names" field in rows, and whichever date field you have in the...

You can use a running total for this. Create: Group 1 on item number Group 2 on size Create a running total which does the following: Maximum of Qty on Hand Evaluate on change of field "size" Reset on change of group "item number" Pop the running total in group footer 2. Create...

There is no way that I can think of to do what you want using a cross-tab because when using cross-tabs you are effectively grouping your data and are forced to use summaries of some sort. The report is fairly easy to create, however, using regular old groups on "name" and "month" (date)...

Try GroupName ({TBL1.FIELD1}) + ' - ' + TOTEXT(round(Count ({TBL2.FIELD1}, {TBL1.FIELD1})),0) PS: you only need to use CSTR or TOTEXT when concatenating using the "+" operator. If you use the "&" operator then the operands will be converted to strings implicitly.

Sorry, small mistake. Don't use "details a" for the column headings, because you'll obviously repeat them for each line (which you wanted to avoid). Rather split group header 5 (or whichever is your lowest level group) into "a" and "b", and then use the above formula for group header b.

Hi Jason Try creating a "details a" section for the column headings, and a "details b" for the actual detail. Then pop into the section expert and use a formula to conditionally suppress "details a" until you are drilled down to group 5. Use the "DrillDownGroupLevel" function to determine how...

Hi Mo. Just out of interest, when you were experiencing problems with the summary field, did you have any group selection formulas or top/bottom N stuff in your report?

Hi Judy. As of version 10 (I think) the column headings automatically inserted for detail fields by Crystal are not quite the same as regular text objects. Their size is directly tied to the size of the detail field itself, thus the "can grow" option is unavailable for these fields. Since...