Weird behavior with Dictionary Object

Hi folks.

Apparently there is something important about using the Dictionary object that I don't understand, and it's driving me up the wall.

I'm opening a recordset and reading from a MySQL database, with a query like this:

strSQL = "SELECT country,timezone FROM " & oTablename & " WHERE receipt LIKE '%" & oReceipt & "%'"

Then the values returned are stored to a dictionary object like so:

Session("MemberRecord").Add "country", RS.fields("country")
Session("MemberRecord").Add "timezone", RS.fields("timezone")

Then the database cleanup:

RS.close
Set RS = Nothing
oConn.Close
Set oConn = Nothing

For troubleshooting I inserted the following two lines:

Response.write "RS.fields('country') = " & RS.fields("country") & "<br>"
Response.write "Session('MemberRecord')('country') = " & Session("MemberRecord")("country") & "<br>"

Now the problem:

Both of the Response.Writes display the correct value IF those two lines are placed BEFORE the database cleanup.

If placed after the database cleanup, the attempt to write the RS.fields value fails as is to be expected. However, what I can't explain is why printing of the dictionary element also fails at this point. All it returns is:

error '80020009'
/filename.asp, line 160

Where line 160 is the Response.Write.

Surely the contents of the elements of the dictionary object shouldn't be dependent on keeping open the database that its values came from!

And I haven't had any success trying to fathom a reason from that error number.

Can someone PLEASE throw some light on this behavior.

TIA

try w/o .add

I gave up on the dictionary object and took a different approach, as it was taking too long to sort out.

However I'll revisit this in a couple of days and try your suggestion.

So is there a known problem with .Add ???

TIA