>  One of the potentially long operations is DmQuickSort, which because 
> it is all happening in a single API call, is neither interruptable (can't
> use a Cancel button on screen) nor do I have access to spin a beach ball.
> Has anyone else dealt with this issue and figured out how to work around
> it (short of bloating your code by implementing your own sort routine)?
>

Your comparison routine is called quite often during a sort; you can make
calls from within there.

I had a case where I was doing a database sort while I had a MNP serial
connection going; large numbers of records caused my connection to time-out.
I added a call to keep the connection alive within my comparison routine.

Neil

Reply via email to