Hi All

I am running a routine which continually repeats a query from an ODBC source to 
sync some data.

There seems to be a problem with the driver that over time the  .EXE I have 
created takes up more and more memory until it goes bang.

If I change this to query from a different source requiring a different driver 
I don’t have an issue (i.e. I’m happy it’s not me 😊 )

I would like to keep the EXE running rather than scheduling it to run close run 
close etc.  As I have a log on the screen showing a visual status of the query 
and when it was last completed.

I am now thinking there must be an easy way to fire off this query in a 
different datasession or thread so that any problems caused by the ODBC driver 
are lost after each execution, any brilliant ideas?



Post Messages to: ProFox@leafe.com
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: 
** 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.

Reply via email to