>Dragan,
>
>>If your grid happens to try to refresh while your code is running in another DS, that may happen - it wouldn't be able to find its recordsource. But then you can always bracket the code with lockscreen, and avoid refreshing meanwhile.
>
>That might be a good solution, never thought about that.

In some frameworks it comes almost naturally (i.e. not my invention). There's the global app object and other such objects which do all the heavy lifting, and it resides in the default DS - you want to let it do its job from wherever you call it, and you pass the current DS number as a parameter where needed. You don't want to refresh during that heavy lifting; you refresh when it's done. It's simply a matter of speed, and along the way it also takes care of this grid problem.

Come to think of it, it would be a problem with any other bound control, or with combos/listboxes with rowsource from an alias or fields. Though those would not just go blank, they'd error.