>Hi Cetin,
>
>'Wait Window' can serve the purpose, but a good progress bar looks professional. It can be used to provide quite useful information. For instance, the progress bar I use can display up to 3 lines of text (each for a separate phase, e.g. preprocess, processing, export, etc. ). As each phase gets completed, it displays a tick mark before the corresponding line. I can change the text in the progress bar (e.g. 'Phase 1 of 5' to 'Phase 2 of 5') and restart the bar from 0 %. Besides, it is not complicated. All I use - Set maxCount property, and a method to set progress bar text and Update().
>
>The problem with 'animated images' is that it continues to suggest that something is going on even if the application has stopped working or failed.
>
>Basically, a progress bar that runs within FoxPro using FoxPro commands gives more control to the programmer.
>
>- Ravi

Ravi,
When a progress bar with some related info is needed you're right. But when all I want to do is to feedback user that I'm working it's just another luggage to carry IMHO. Even I could do informing back with a simple editbox (and I do in cases).
"The problem with 'animated images' is that it continues to suggest that something is going on even if the application has stopped working or failed."
This is no different with a progress bar when it has no relation to what it's doing exactly. Saying 'Processing file x', increasing progbar upon completion, 'Saying processing file y' and stopping for a long time (how much you find MS' progress indicators trustable to say it's working really? - w/o some experience on estimate how long really it should take I don't and find myself checking disk,process activity).
Cetin