I doubt that it's the indexed-reposition that's causing the issue. That should be legal in any query string.
Can you please provide the relevant client logfile lines when the CustomLogEntryType DataAccess is active with Consultingwerk.OERA.LogFetchDataDetails = TRUE.
I'd like to see the source default query, the client query and the resulting prepare string.
The layout of your screens should be irrelevant. The same request should return the same result even from the Business Entity Tester or a 3 liner.
We feel the framework or even Progress should know when to add indexed-reposition to the querystring and that it shouldn't be included in the DataAccess.
Based on which rule-set? I don't think that in the framework we can make up for any shortcomings in the query processing capabilities of the ABL.
The source default query is the database query to which the client filter is added. IMHO this should include indexed-repositiorn