🚀 go-pugleaf

That sort of works, but the main application now reports errors - what I am
doing is retreiving a load of records from a database, and if I interrupt
this with Application->ProcessMessages(), the database reports that it has
lost it's cursor.

Application->ProcessMessages() is the kind of call that I was looking for
though, so thanks for that.

I suppose that I could do with a call that only processes messages specific
to the Comms thread.

"Ron Sawyer" <XXXRSAWYER8128XQQXX@aol.com> wrote in message
news:40efe85b@newsgroups.borland.com...
> Try a call to Application->ProcessMesssages in the main program loop.
>
>
> "Chris Phillips" <chris.phillips@corusgroup.com> wrote in message
> news:40eea7bc@newsgroups.borland.com...
> >
> > I have an application with 3 threads to it.  One thread is simply
> processing
> > serial IO but must run close to real-time - I have given it priority
> > tpTimeCritical.  This thread is executed by the main program.  However,
if
> > the main program is doing something processor intensive (such as
> retreiving
> > a number of database records), then my Comms thread doesn't get a look
in
> > until the processor intensive part has finished.  I have put a Sleep
> command
> > into the processor intensive loop thinking that it will allow the Comms
> > thread to continue with its stuff, but to no avail.
> >
> > Any suggestions?
> >
>
>