Do you have an error handler?
It should not present a UI, that causes an error and could hang the
executable.
You might want to exit with the ExitProcess api when there is an error.
DECLARE ExitProcess IN WIN32API Integer ExitCode
I usually use a negative number when something didn't work right.
ExitProcess(-1)
HTH,
Tracy
-----Original Message-----
From: ProfoxTech [mailto:[email protected]] On Behalf Of Desmond
Lloyd
Sent: Monday, June 11, 2018 5:33 PM
To: [email protected]
Subject: VFP: Task Scheduler
Good afternoon,
Going nuts down here, have a simple executable generated from a single
program. Runs fine by itself. Grabs s few records then sends out an email
via Outlook automation. Which, btw, does Outlook have to be open to
run, or not? In any event if I run it in the task schedule it shows that
it is running, but it never stops or returns to the ready status????
Regards,
Desmond
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
