Kurt Wendt wrote on 2015-05-12:
> I am curious. For this application - are you using Forms? If so - you could
> use the Timer Object on the Form.
>
> -K-
>
Kurt,
First thoughts, Something that needs to run continuously, is probably running
on a server. No UI is needed.
If it is to run in a scheduled task, having a UI causes the task to fail on
Server 2008 and higher.
When this is an unattended program, the following line should be considered.
Sys(2335, 0)
Due to personal experience with Timer's triggering some odd things to happen, I
tend to avoid them.
When you break and look at the debugger, the Timer continues to fire.
If the process that is going takes longer than 5 minutes (unlikely but
possible), the Timer will start the process again. Unless it is specifically
coded to avoid that.
I use the Sleep API call, particularly when the process is a procedural flow,
no UI events to worry with. (With the exception of a Cancel request.) When I
have a UI and need to wait, I use a loop calling Sleep(500) followed by
DoEvents, which prevents the UI from going non-responsive.
Tracy Pearson
PowerChurch Software
_______________________________________________
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.
