G
Guest
Hello.
I write to this forum because I do not know how to otherwise report this bug
that has been haunting my program for a very long time. Today I were finally
able to narrow out the cause of this bug:
1. Create an empty database
2. Create a form, and make the form a popup, blocking and with dialog frame
3. Add a button to this form
4. Write a OnClick VBA handler:
Dim X As Date
X = Now
While DateDiff("s", X, Now) < 20
DBEngine.Idle
Wend
DoCmd.Close acForm, Form.Name
5. Close the form, and open it.
6. Click the button.
7. The waiting loop starts to run. After a while, Windows XP gets impatient,
and marks the Access application as being "not responding". When the wait
loop completes, the form is being closed, and for some reason Access is left
in a coma.
If anyone has more info about working around this bug, or hits for how to
troubleshoot more, or on how to best report this kind of bug, I would greatly
appreciate the info.
I write to this forum because I do not know how to otherwise report this bug
that has been haunting my program for a very long time. Today I were finally
able to narrow out the cause of this bug:
1. Create an empty database
2. Create a form, and make the form a popup, blocking and with dialog frame
3. Add a button to this form
4. Write a OnClick VBA handler:
Dim X As Date
X = Now
While DateDiff("s", X, Now) < 20
DBEngine.Idle
Wend
DoCmd.Close acForm, Form.Name
5. Close the form, and open it.
6. Click the button.
7. The waiting loop starts to run. After a while, Windows XP gets impatient,
and marks the Access application as being "not responding". When the wait
loop completes, the form is being closed, and for some reason Access is left
in a coma.
If anyone has more info about working around this bug, or hits for how to
troubleshoot more, or on how to best report this kind of bug, I would greatly
appreciate the info.