Memory leak in ODBC driver

Question

I have a serious problem with the maxdb ODBC Driver. I tested Version 7.06.03.00 and some older Versions.
Here is a little example for MS Access to show the problem. The table "artikel" is a linked maxdb table. The example code opens and closes a recordset in a loop. You can see the memory usage in the task manger going up and up. If you have many recordsets in the table, the system is crashing when it is going out of memory.
If i change the linked table to for example a mysql-table the memory usage is stable. So I think there must be a memory leak in the maxdb odbc driver.
Example code:
Sub memtest()
Dim RS1 As Recordset, RS2 As Recordset, DB1 As Database
Set DB1 = CurrentDb
Set RS1 = DB1.OpenRecordset("select id from artikel")
Do While Not RS1.EOF
    Set RS2 = DB1.OpenRecordset("select * from artikel where id=" & RS1("id"))
    'do something
    RS2.Close
    Set RS2 = Nothing
    RS1.MoveNext
Loop
RS1.Close
Set RS1 = Nothing
DB1.Close
Set DB1 = Nothing
End Sub
I hope you can follow me and find the leak.
Thorsten

Answer 1

Hello Thomas,
thanks for your tips, but they did not help. Activating Connection Polling did not change anything. And opening another connection did not help, either. I did it the following way:
Sub memtest2()
Dim conODBC As New ADODB.Connection
conODBC.ConnectionString = "Data Source='xxxx';User ID='xxx';Password='xxx'"
conODBC.Open
Dim Rs1 As Recordset, Rs2 As Recordset, DB1 As Database
Set DB1 = CurrentDb
Set Rs1 = DB1.OpenRecordset("select id from artikel")
Do While Not Rs1.EOF
    Set Rs2 = DB1.OpenRecordset("select * from artikel where id=" & Rs1("id"))
    'do something
    Rs2.Close
    Set Rs2 = Nothing
    Rs1.MoveNext
Loop
Rs1.Close
Set Rs1 = Nothing
DB1.Close
Set DB1 = Nothing
conODBC.Close
End Sub
Perhaps one of you has another tip how this can be done.
@Lukasz:
using a seperate ADODB.Connection works fine, but that does not solve the problem itself. At first I would have to rewrite much code and the second much bigger thing is that the memory leak occurs even when working with bound forms in MS Access. For example: I have one large form with many subforms on it. If i go from record to record on this form the memory usage is increasing dramatically fast and there is no way to influence what kind of connection MS Access is using for bound forms.
Regards
Thorstem