Hello
I've got a simple question about TOraQuery.
I have noticed a difference in behaviour between blocking / non-blocking mode after calling <TOraQuery>.Refresh method.
In blocking mode current record in most cases stays the same, but in non-blocking mode it looks like always resetted to first record.
Is it even possible to maintain current record in NonBlocking mode after <TOraQuery>.Refresh without any extra code?
Regards
P.C.
[fixed in 9.7.25] Maintain current record after Refresh call in NonBlocking mode
[fixed in 9.7.25] Maintain current record after Refresh call in NonBlocking mode
Last edited by pcz on Tue 28 Jun 2016 08:01, edited 1 time in total.
Re: Maintain current record after Refresh call in NonBlocking mode
Thank you for the information. We have reproduced the issue and will investigate its origin. We will inform you about the results shortly.
Re: Maintain current record after Refresh call in NonBlocking mode
Are there any news in this subject? 

Re: Maintain current record after Refresh call in NonBlocking mode
We have already fixed the error, and the fix will be included in the next build. We plan to release the build this week.
Re: Maintain current record after Refresh call in NonBlocking mode
Problem solved in version 9.7.25 
Thanks!

Thanks!
Re: [fixed in 9.7.25] Maintain current record after Refresh call in NonBlocking mode
Glad to see that the issue was resolved. If you have any further questions, feel free to contact us.
Re: [fixed in 9.7.25] Maintain current record after Refresh call in NonBlocking mode
Looks that I've got some side effects of this fix with my code too...
viewtopic.php?f=5&t=33059&p=117311#p117311

Happens always after <TOraQuery>.Refresh call when query returns exactly one record

viewtopic.php?f=5&t=33059&p=117311#p117311

Happens always after <TOraQuery>.Refresh call when query returns exactly one record