Hi John,

Ok, but I don't have a patience to wait 20 min. while operation is completed. I should not report it as a hung, right. Let's report it: the results are unknown due to impatience of the operator :)

>Hi Nadya,
>
>No no no no.....perhaps you do you not understand what "not responding" means? That message indicates that the application is not servicing UI events, not that it had completely hung. VFP does not check the event queue during monolithic routines that do not invoke UI objects or make calls outside the current procedure.
>
>Dave was right...but you misinterpreted his response. There is a big difference between a frozen app and one that does not respond to events.
>
>>>
>>>>I've just tried it at home on Win 98 with 64MB RAM. I was not patient enough to wait, so I had to kill VFP. It didn't show a first message in ~ 20 min.
>>>
>>>Then you shouldn't report that VFP hung during the test.
>>
>>Why not? 20 min. for the first operation - how should I call it? It showed "Not responding", when I hit Ctrl+Alt+Del
>>
>>At work first and second operations worked. It hung on the last one.