msbaccessdba
Sep 27 2005, 08:09 AM
Lately, my forms have been hanging behind the scenes (usually acDialog forms) when a user clicks a button, etc. I haven't found a direct cause and it's boggling my mind because they've been working fine...until now. What I mean by "hang" is that they are not responsive to the user.
I'm thinking the user clicked something else prior to or didn't follow the procedure and isn't telling me.
Any ideas on how to check this or find out exactly why my code has suddenly begun to hang?
HelloAgain
Sep 27 2005, 09:35 AM
One thing I can recommend is the old fashioned method of inserting a bunch of message boxes at various points of your code. For example:
<code>
MsgBox "A"
<code>
MsgBox "B"
<code>
MsgBox "C"
<code>...
Once a message box fails to open, you know the code hung somewhere after the last successful message box and before the first failed message box.
msbaccessdba
Sep 27 2005, 09:38 AM
I may have found it in b/n here and there. It was trying to grab a value from a control in a subform that didn't exist and would just sit there (gosh knows why). I believe I fixed it. I use the MsgBox debug (v. breakpoints) sometimes when I must absolutely know what values are being created (as opposed to the Watch function). Thanks for your help.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.