Nadya,
I'm afraid I couldn't understand the problem. I should have at least steps to reproduce it.
Yes, sure I haven't seen that. Interestingly though I don't even know a way to make scrollbar stop moving (except blocking click on it).
Cetin

>Hi Cetin,
>
>All three of you disagree with this idea. I think, I'll discuss it again. Perhaps, we should still use tablebuffering, but make revert to work on one record only. However, in TableBuffering Save operation takes a long time on big files. I used record buffering in couple of my applications and I don't have problems so far, but save operation works much faster and all other operations too. I don't use calculations with moving record pointer (except perhaps one application, which I have to check carefully again).
>
>Still the problem with scroll button remains. Are you sure, you've never seen this?
>
>BTW, I have another problem. I have my table sorted by Situs index (upper(ccode+town+street+str(stNum,4)+stNumExt+Unit). Now, if user changes street name, then hit next/previous button, he/she moves to completely different place, where he/she was before. Do you know, what would be the best place to change this behavior? And how? All forms use our standard BaseForm class with navigation bar, which has standard buttons like top previous next bottom etc.
>
>>>Hi everyone,
>>>
>>>I noticed, that if we use Table Buffering (BTW, we decided today to switch to record buffering, because it's dangerous, that user may hit revert button and revert all changes made), when we try to move scroll button on scroll bar, it doesn't move and stays unchanged. I'm wondering, if somebody else experienced this behavior and does it have a cure?
>>>
>>>Thanks in advance.
>>
>>Nadya,
>>No never experienced and almost everytime my grids use table buffering. I would suspect something else like an invisible shape, code not letting move vice versa.
>>Switching to record buffering in grid sounds shooting yourself on the foot. You can behave as if you were doing record buffering in code selectively. Or if you're pessimistic work with a nonbuffered cursor and update base as appropriate.
>>Cetin