>Any advice on how to handle the following:-
>
>One form in my application has a timer that triggers every 15 minutes.
>This runs code that can last up to 2 minutes (sending and retrieving emails using westwind).
>
>In the meantime the user is "stuck", as the form they were working on is not available until the code has finished running.
>
>What can I do to give the user a better experience?
You could put the "2 minute" code in a separate .EXE. Then you could either:
- run that .EXE in parallel with the user's code and have a 15 minute timer in it
- have no timer in it; instead, call it from your existing timer asynchronously via the ShellExecute API function, Ed Rauh's API_AppRun class, etc.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up
