RIPARAM Slow Record Retrieval

[Mike_Cutts]

Hi,____We have a view in a Sybase database which contains around 51,000 records. I have designed a report against this view and fired it up via a control table text file. ____One of the entries in the text file passes a value to the report (for argument^s sake lets call the optional entry Text1). I have then created a calculated field on the report whose expression looks something like RIPARAM(^Text1^)____Following this I created a filter on the report to only include records where a field in the view matches the value contained in the calculated field.____The problem is that when the report is executed it takes an age to bring through any data. However, if I put the contents of the Text1 entry directly into the filter, the correct record is displayed more-or-less straight away.____Any help (if you can understand the terrible explanation) on this problem would be greatly appreciated.____Thanks,____Mike.

[kfleming]

The reason this happens is that the filter expression is being evaluated locally rather than being sent to the SQL engine.__You would be better off to use one of the new parameteRR fields in place of the RIPARAM or else use RI_WHERE instead of RI_FILTER so that the where is passed directly to SQL.____Kathleen__R&R Support

[Mike_Cutts]

Thanks for that, will give it a try.