>I'd like to have my own progress bar in use when I
>perform SQL selects.
>
>Anyone know how to do this?
>
>Thanks

Hello Kevin;

It is nice to let the user know that something is going on. Impatient users have been known to “pull the plug” while waiting for the Fox to finish an operation like a Select statement. We all know what can then happen.

User feedback is something that is driven by the client. If they want progress bars then you must explain that it will slow down an operation from 10 – 15 times what it would otherwise be. There may be a greater need for feedback than speed.

I have many progress bars I have used over the years. Some are more accurate than others. You can even use an OLE control for this purpose. I have such a control (form) which I played around with and if you would like a copy of the class to play around with I would be glad to send it to you.

Here are some links on the subject:

http://portal.dfpug.de/dFPUG/Dokumente/MigrationSourcebook/Using%20the%20Progress%20Bar%20Control%20in%20Visual%20FoxPro.doc

http://fox.wikis.com/wc.dll?Wiki~ProgressBarClass~VFP

http://fox.wikis.com/wc.dll?Wiki~PushPopSQLProgressBar~VFP

http://www.west-wind.com/wwvfppd.htm

I do like Nancy’s idea about breaking up the select statement. That can be a good approach to allowing user feedback. One way to do this would be to have a wait window pop up between select statements.

I remember a wait window being used to give feedback by updating the number of records processed and the total number of records. It was super slow because it made one pass at the select statement to determine the total number of records. It was very accurate but like a dead snail when it came to speed.

This is all a tradeoff and depending upon the user requirements and length of the select statement, one approach will have an advantage over another.

Tom