Access 2002 Runtime Fails to End

[J-P-W]

I have now found that when a user, with Access 2002 Runtime, closes,
correctly, their database and then I look at Task Manager MSACCESS.exe
is still running. Unless that running process is killed the database
will not launch (i.e. Access won't allow a second version running?)

I've played around using the /runtime switch also and found that on
_one_ occasion that did the same.

Anyone aware of this 'bug' and also know how to cure it?

Thanks

Jon

[Bob Quintal]

"J-P-W" <jo******@gmail.com> wrote in
news:11**********************@f14g2000cwb.googlegr oups.com:

I have now found that when a user, with Access 2002 Runtime,
closes, correctly, their database and then I look at Task
Manager MSACCESS.exe is still running. Unless that running
process is killed the database will not launch (i.e. Access
won't allow a second version running?)

I've played around using the /runtime switch also and found
that on _one_ occasion that did the same.

Anyone aware of this 'bug' and also know how to cure it?

Thanks

Jon

There are lots of possible reasons for access refusing to close.
The most common culprit is code which opens (sets) an object
reference but fails to close the object when finished with it.

if you :
Dim rs007 as recordset
set rs007 = currentdb.openrecordset(strSQL)
or
Dim frm01 as form
Set frm001 = mainform

You need to make sure that you:
rs007.close
set rs007 = nothing
frm001.close
set frm001 = nothing.

Many people say the "= nothing" is not required, others insist
it is.

--
Bob Quintal

PA is y I've altered my email address.

[J-P-W]

Thanks Bob, I've had a search through the code and there are some set
that aren't closed, so I've pepppered it with set xx = nothing's

Many thanks, Jon