On Oct 15, 2006, at 1:23 PM, Scott Goelzer wrote:
I could use some database guru advice. I currently have a database
front end that require significant data processing after data is
entered or changed. Currently, I have a hidden window that runs a
timer and keeps and checks which records need reprocessing and does
them one at a time, allowing the interface to mostly continue. This
is ugly (but works). I am trying to learn threads in order to
improve this (not easy since the examples seem to focus on showing
the extremes of threads, not how to set a simple use and there is
almost nothing in the documentation).
How does a RealSqldatabase handle both a thread and the main
program making calls to the same database? How am I supposed to
handle it? Should I even pursue this?
make every thread have it's own connection to the database and you
should be fine
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
