>
>Especially if your app allows customers to perform ad hoc queries; you're going to get table scans that can take many seconds or even minutes in large databases.
>
>FWIW, we tried an image control with one of those fancy rotating "working" gifs, but that also tended to freeze during ODBC querying, presumably because single-threaded VFP is set not to yield to waiting ActiveX or gifs. Perhaps the VFPX Asynchronous project has an answer; display a gif in its own thread and it should swirl merrily away. However, KG made the point that a gif that swirls attractively forever after something went bad in the query, isn't a lot of use either. I might raise it with Chuanbing to see whether VFP can be persuaded to yield via an event or whatever while it sits and waits for ODBC... the user just needs to know it's not actually stalled but working hard.

Was thinking along similar lines, but have no ready soluion like Walter has. My idea would be - whenever ODBC is set to return batches - to update a counter with #batch received[, #records received]
This would give easy way to see if server is still churning or too much data / too slow connection is current bottleneck.

my 0.02€
thomas