ODBC/Error

Hello A few weeks ago, I complained about not getting a response to my feedback reporting an error with ODBC in /Command. As I still have no answer, I am asking the list, how do you handle severe ODBC errors. The special error I get when pulling the network plug from a computer connected to an Oracle Database via ODBC. I can catch the first error occurence, but after recovering my script throws an second (ODBC) error executing commands doing nothing with ODBC. If I catch the second error too, Rebol starts to consume MB of memory very soon. So this is no real help. Has someone a solution to this? TIA AR -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen!

Try a different database with different ODBC driver (Mysql for example). Then you can rule out that that's the one consuming the memory and causing the problems. --Maarten

For some reasons Mysql is no viable alternative. But I will try with some different drivers when I have some time. Additonally I will try what a unloading and loading of the ODBC driver will do. Unfortunately RT has no Free for ODBC, although they provide it for the DLL API. AR

> Try a different database with different ODBC driver (Mysql for example). > Then you can rule out that that's the one consuming the memory and > causing the problems. > > --Maarten >

I used different drivers and the waste of memory is directly correlated to the amount of memory I allocate in REBOL. Just the internal garbage collector is no longer working. This is also indicated by the fact, that the most following errors happen near an recycle. AR

> Try a different database with different ODBC driver (Mysql for example). > Then you can rule out that that's the one consuming the memory and > causing the problems. > > --Maarten >

What command version are you using? There are intermediate builds that have bug fixes in the gc. If you are using 2.0, go to rebol.com and ask for a more recent build. Perhaps that helps. --Maarten