>> Based on the answer Sergey gave you, I chose not to use ENGINEBEHAVIOR 70
>> if at all possible and stopped using views and the data environment too.
>> I had views where these problems existed. I ended up having to break the
>> queries into two or more parts. That raised the issue of how to reorder
>> them in the DE so the "subselects" fired first. SPT and data objects are
>> more flexible and therefore easier to maintain IMO.
>
>It's just a matter of knowing what the rules are, and where the mice are that made the system.
The problem is that, as far as I know, there is no guarantee that you will always get the last physical record from the table. It may be that it currently works so, but that the behavior changes in future versions.
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)