Scope problem

[Bruce]

Hi,____I am using R&R 12.0.002. I call the rrwrun from my application and use a text file with hiscope and loscope set in the text file. 99% of the time it works fine - however, if the database has two record with near identical keys - one ends in A and the other ends in AA then the report prints records both A and AA. If I set the scope in the actual report designer and run the report it works fine. What appears to be happening is that, when a report is run from rrwrun, it trims the scope and then uses the length of the scope to limit the report run scope. Thus a scope that is 19 char. long will also report on the other possible combination of a 20 char. long scope and the result includes the A as well as the AA record.____Is there a fix or work around for this issue?____Best regards,____Bruce__

[kfleming]

I just tried this and you are correct that it is not working. One workaround though is to set RI_SCOPE to a ? to prompt the user to enter the high and low scope values.____Kathleen__R&R Support

[Bruce]

That would not be a viable work around as I have hundreds of users running thousands of prints using this function daily. When can this issue be fixed in the R&R product?____Best regards,____Bruce__

[kfleming]

We will fix this in a future release. Until then you could use a combination of scope and query to get only the records you want. That can all be done within the text file so no user intervention at runtime would be required. Just a bit more code to set the query along with the scope.____Kathleen__R&R Support

[Bruce]

Kathleen,____Thank you for the suggestion. I have applied a fix by inserting a space in the code so that any item that ends with a single char. has a space inserted before the char. - thus (space + A) will scope correctly when compared to AA. But the fix would be very useful to prevent this in future.____Best regards,____Bruce____PS: Will you email me when the fix is available?______