Search results for query: *

You could get this error if the string field {CloseTime} does not contain a valid time string in any record. You need to validate this field and provide a default time alternative.

Barbara's method also works, and when the subreport is based on a parameter-using stored procedure or query, it must be used to pass the parameters correctly to the sp or query. Be sure to scroll the subreport parameters list to find the correct entry - CR will create a new parameter for you if...

Join tables V_FORM_NAME => V_FORM_COUNT with a Left Outer Join to include all records in V_FORM_NAME and only those records from V_FORM_COUNT with a matching {FORM_FILE_NAME} field. Where no matching record exists, V_FORM_COUNT fields will be NULL.

Use Subreport Links to pass the parameter values to the subreports. In the Subreport Links dialog, select the parameter fields into the "Fields to link to" list. For each of these fields, check "Select data in subreport based on" and select the appropriate subreport data...

A subreport inserted into a detail section will be printed once for each detail in the main report. If you only want it once, put the subreport in a report header or footer. The subreport record selection should be limited by the linking value if the link has been entered correctly. In the...

with standard fonts like Times NR or Arial, chr(189) should work.

Be aware that the imported subreports' page headers and footers will be converted to (print-once) report headers and footers, and that the container report page headers and footers will be printed on the subreport pages. You can deal with that but it will take some work.

Go to http://support.crystaldecisions.com and check out SCR_Oracle_Stored_Procedures.pdf

From the menu: Insert/Field Object/Database Fields. Select a field and drag it onto the report design view. If you need to add database tables, use Database/Visual Linking Expert.

Don't know - I've never done that. What integration method are you using -- RDC, OCX, CRPE? -- and from what environment -- VB, web page, other??

SQL Designer is a separate application that is part of the CR installation package. It creates a .qry file that can be used as a data source for a report. It sound like you are already using some sort of front end to call CR(??). You can pass a record selection formula or parameter values or a...

CR builds its SQL Query using the tables and links from the visual linking expert and the fields you have either placed on the report design or referenced in formulas or groupings. You are not allowed to edit the SELECT part of the query in the View SQL dialog and you cannot use subqueries at...

To get rid of the box, right click on the subreport object (on the main report design) and select Borders; then set all borders to "None". Make the subreport object and the section it is in as small as possible. You can suppress all the sections of the subreport in the subreport...

Conditionally suppress the section. In the Section Expert, select the section and click the x-2 button next to "Suppress". Enter a formula which evaluates to True for the condition that will suppress the section, e.g. {?UserOption} = "Percentage"

Make two cross-tabs in two sections and suppress one or the other based on the user selection

This is a way to convert a multiple selection parameter to a concatenated string which you can pass to your stored procedure: Create a dummy main report which uses a one-record data set (anything simple will do). Create a multiple-selection parameter for this report. Add a formula in the report...

<<Mid(Replace{sgpso203.DESC},&quot;.&quot;,&quot;&quot;,4)>> You need another set of parens: Mid(Replace({sgpso203.DESC},&quot;.&quot;,&quot;&quot;),4)

Go to the Record Selection formula and add &quot;Not IsNull({MyTable.Comments})&quot; -- selecting the Comments data field from the list of available field. That should select only records with Comments entries. You cannot use memo fields in formulas -- except for IsNull. Then group by User.

You may have a blank report footer section that spills over onto the second page - if that's it, just suppress the footer and/or close it up. (What's in the left gray margin on the second page should show what report section it is). Another possibility is that you have &quot;New Page After&quot...

You should be able to edit or re-enter the formula (that produced the error that started this thread), selecting the summary field from the Fields list - if it's there, then the &quot;The summary/running total field could not be created&quot; message makes no sense. Um. Unless it's the...