Unexpected returned table rows on client side

Hi,
This initially also crashes but when specifying RemoteFetchEnabled:=False; it works.

Thanks for the help,
FYI: I still think it should report an error instead of returning a partial dataset when somebody tries to do what I did

it isn’t error. in some cases it can be used for creating specific conditions: for example user can want to skip X records and write the rest …

Hi Evgeny,
I think you still don’t get the issue but nevermind.

if you create simple testcase with this issue, I’ll review it and add to our tests