[AccessD] Runaway Form?

Dan:

"If you haven't already, import the frmMainMenu to a new Access file, then
back again to 'renew' this form. "


THAT DONE IT!!! 

Mil gracias.

Rocky
 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: Monday, November 30, 2009 4:56 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Runaway Form?

For testing:

Create a new blank form named: frmCPUTest

Create a new item in your Main Menu to open the above form.

Bit by bit, copy code and controls to the form frmCPUTest from the form
frmMainMenu, until the new form has identical functionality to the original
form.  Test the new form for CPU usage after each change.  If the new form
never does spike the CPU usage, then that's your new form!  Otherwise, you
should be able to see what in particular about the frmMainMenu is causing
the problem.

Good Luck!

PS - If you haven't already, import the frmMainMenu to a new Access file,
then back again to 'renew' this form.  You could also try a
Decompile/Compile and then a Compact/Repair.

Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Monday, November 30, 2009 6:39 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Runaway Form?

Dear List:

I have a simple bound form.  When I open it and it is (apparently) just
sitting there waiting for me to do something, the task manager shows Access
using 50% of the machine cycles (I discovered this because whenever I opened
the app the fan in the comp would fire up).

I put break points in all the modules behind the form, and breakpoints in
all the public functions to see if I could catch it doing something.  

The form is called from the Main Menu.  So in the called form Open event, I
put Docmd.Close acForm, "frmMainMenu" and the CPU use for Access went to
zero.

So It's apparently something about leaving the Main Menu form open with the
called form.  I put breakpoints in all the modules behind Main Menu.  Didn't
break anywhere. I tried putting an open Main Menu command in the called
form's exit routine, but the Main Menu didn't open. 

This is pretty plain vanilla stuff and I've never seen this before.  So I'm
kind of stumped.  Has anyone seen this behavior before or have any ideas on
how to track down the problem?

MTIA

 

Rocky

 


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com