>I would rather not put the batch into a thread; if I do this i will >have to manually inactivate menus other user interactions. I like the >fact that user interaction is highly restricted during batch >processing. Plus, putting batch execution into a thread might be >slightly slower.
I guess with App.DoEvents you'd have to deactivate your menus and other user interactions as well, so you might as well go with a thread then. I know of no methods to keep parts of the user interface responsive and others not, unless you disable/enable them yourself. Marc _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
