Subform not unloading

[Pamela via AccessMonster.com]

Hi.

We have been having trouble with a DB leaving the .ldb file, and leaving
MSACCESS.exe in the processes list in the Task Manager. I ran across
something yesterday which suggested a subform wasn't unloading when the
application is closed.

I went in and placed a msgbox in each subform's unload event, and sure enough,
there is one form which is loading, but not unloading.

What is the proper syntax for getting a subform to unload and where would be
the best place to place the code? On the main form's On Close or On Unload
event?

I'm also wondering why the one subform wouldn't be unloading, and if it's not
would it be causing the symptoms of leaving MSACCESS.exe running under
processes in the Task Manager?

Any help would be appreciated. Thanks!

MS Access 2002
Windows XP - the Database in question is on a network share.

 

[Jeff Boyce]

Pamela

Windows XP - the Database in question is on a network share.

<snip>

Is there a chance that the entire database is on the share? Whether you
have split the database to Front-end/Back-end (a very good idea) or have a
single .mdb file, keeping the piece(s) on a network share and using desktop
PCs to open/launch that opens Access to considerable risk of corruption.

 

[Pamela via AccessMonster.com]

Thanks for your response. I do plan to split the database once it is fully
completed (though it is currently being used). As it turned out, I *thought*
the problem was with a sub-form not unloading that was keeping Access.exe
running in the task manager. I found my fix (here at this great forum):

http://www.accessmonster.com/Uwe/Forum.aspx/access-modulesdaovba/5933/Locking-Files


"As for bugs, the first one that comes to mind for Access 2002 is one
that I have personally documented, which is associated with conditional
formatting applied to a calculated control. After displaying a form
with conditional formatting applied to a calculated control using the
"Field Value Is", "equal to" option, MSACESS.EXE remains in memory
(shown in task manager's list of processes) even after both the form and
application are closed. If this is the bug that's biting you, I am told
that it has been corrected by SP3."

My symptoms of multiple instances of Access.exe in the task manager (under
processes) is what led me to the solution.

Of course, I work for a large corporation & they only have SP2 installed, so
when I saw that quote, I hoped I had found the problem...I had! This will
make a lot of users very happy.

The "help desk" here had this for a solution: "Access is flaky so we won't
support it". Nice, huh?

Anyway, thanks for the help.

Pamela

Windows XP - the Database in question is on a network share.

<snip>

Is there a chance that the entire database is on the share? Whether you
have split the database to Front-end/Back-end (a very good idea) or have a
single .mdb file, keeping the piece(s) on a network share and using desktop
PCs to open/launch that opens Access to considerable risk of corruption.

Hi.

[quoted text clipped - 17 lines]

MS Access 2002

 

[Jeff Boyce]

Pamela

You're welcome. Congratulations on finding a fix.

I'll still suggest that if you have multiple users "sharing" a single
instance of an Access .mdb file, located on a network share, it is probably
"when", not "if", you will have a problem with corruption. Plus the network
geeks may come looking for you due to excessive use of network bandwidth for
pushing the components back/forth over the LAN.

Regards

Jeff Boyce
<Office/Access MVP>

Thanks for your response. I do plan to split the database once it is fully
completed (though it is currently being used). As it turned out, I *thought*
the problem was with a sub-form not unloading that was keeping Access.exe
running in the task manager. I found my fix (here at this great forum):

http://www.accessmonster.com/Uwe/Forum.aspx/access-modulesdaovba/5933/Locking-Files


"As for bugs, the first one that comes to mind for Access 2002 is one
that I have personally documented, which is associated with conditional
formatting applied to a calculated control. After displaying a form
with conditional formatting applied to a calculated control using the
"Field Value Is", "equal to" option, MSACESS.EXE remains in memory
(shown in task manager's list of processes) even after both the form and
application are closed. If this is the bug that's biting you, I am told
that it has been corrected by SP3."

My symptoms of multiple instances of Access.exe in the task manager (under
processes) is what led me to the solution.

Of course, I work for a large corporation & they only have SP2 installed, so
when I saw that quote, I hoped I had found the problem...I had! This will
make a lot of users very happy.

The "help desk" here had this for a solution: "Access is flaky so we won't
support it". Nice, huh?

Anyway, thanks for the help.

Pamela

Windows XP - the Database in question is on a network share.

<snip>

Is there a chance that the entire database is on the share? Whether you
have split the database to Front-end/Back-end (a very good idea) or have a
single .mdb file, keeping the piece(s) on a network share and using desktop
PCs to open/launch that opens Access to considerable risk of corruption.

Hi.

[quoted text clipped - 17 lines]

MS Access 2002