> > 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? >
Memory is allocated on the process level and not automatically freed when the thread that allocate a block is terminated. If it is a faulty driver, you need to create a new process from time to time. Options would be to put this part of your application into a EXE COM Server that you occasionally release and re-create, a separate EXE that you launch or by letting your application restart itself every x iterations. You haven't said anything about which ODBC driver this is. Maybe there is an updated version available? Or maybe there is another vendor with drivers for the same database (Oracle DBs have multiple options, for instance). -- Christof -- foxpert GmbHUlzburger Straße 352 22846 Norderstedt Tel. Zentrale: (040) 605 3373-70 Fax: (040) 605 3373-75 http://www.foxpert.com <http://www.foxpert.com> Registergericht: Amtsgericht Kiel, HRB 19260 KI Sitz der Gesellschaft: Norderstedt Geschäftsführer: Christof Wollenhaupt --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ 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/cal4qjhg5nnrd3rrkwmflv9p4oubpxv_b237ngxnif82gjcu...@mail.gmail.com ** 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.
