vb6 - Can dao350.dll get corrupted in memory and corrupt new connections? -

we trying resolve problem involving access database connections. goes fine hours or days. program gets page fault error. after that, every program on network unable communicate access databases until every program using access shut down.

the programs vb6 (yeah know).

they use dao350.dll using reference:

dao2535.tlb#microsoft dao 2.5 object library

it seems have orphan dlls in memory - don't belong process.

see image.

has encountered this? if how did resolve it?

our programs running on server 2012 (that seems system happens on if helps).

i'd appreciate can this.

thanks.

first, pls not apologize using old code.

i can still things vb6 , vb5 impossible of newer 'lock down' ugly semantic stuff have today.

my guess declaring recordsets within code not being correctly terminated.

to explain,

both vb5 , vb6 claimed private variable, or procedure variable went out of scope when procedure finished.

but, not true recordset variables.

assume following

dim dbs database dim rst recordset dim ssql$  set dbs = currentdb  ssql = "select * tbl_name" set rst = dbs.openrecordset(ssql)      ... things  set rst = nothing set dbs = nothing 

so, assume rst went out of scope (closed, freed memory).

it did not!

one must affirmatively close rst object

rst.close: set rst = nothing set dbs = nothing 

otherwise mem occupied, albeit orphaned.

over time, creates 'memory leak'. when memory gets re-used, causes problem describe. kinda clogged arteries causing heart attack.

you should inspect code make sure rst objects (including rst clones) being closed.

this assumes not using api's move memory around. can cause similar issues, doubt build on time (like heart attack). move memory issues more shiv in gut heart attack. happen straight away , far easier find.

hth,

gary