>hi,
>thank you
>
>I suspect that your report works directly with the table, "mstr". If you delete all tables from the report's DataEnvironment, the report will use the table or cursor in the active workarea, instead. In this case, the records just selected with the SELECT - SQL command.
>
>i try many ways, but nothing happend , how i can do that.
>
>best regards.
>m.qasem
Do I understand correctly, does it work now?
Tables in a Report DataEnvironment are a frequent cause of headaches, in my experience. If the report behaves weirdly, that is one of the first things that should be checked.
Perhaps your original solution would have worked too, by just removing the report's DataEnvironment - but then, I didn't quite understand what the problem was.
Anyway, using SELECT to prepare the cursor, as I showed you, should help to keep your program simpler. Note that in my version of the code, the condition is specified only once.
There is another simplification which I forgot to mention, which you can use in your code: the use of between().
x >= a AND x <= b
is equivalent to:
between(x, a, b)
Because the comparison is always for > = and < =, in some cases it might still be necessary to use the < and > operators.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)