By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
431,966 Members | 2,054 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 431,966 IT Pros & Developers. It's quick & easy.

Click causes crash

P: n/a
I am front ending a SQL Server database with MS-Access 2000. The UI has
many buttons that launch VB code. One of the buttons launches a lengthy
process that takes 20-30 seconds to complete. If the user starts
clicking their mouse off of the active window the Access Toolbar
displays Microsoft Access (Not Responding) and then moments later a
hard crash occurs and is announced by a system dialog box. When the
user clicks the OK button in the dialog box Access terminates and needs
to be restarted.

Things I've tried:

Popping up a form announcing "Processing". The form has both Pop Up and
Modal attributes set to Yes. (BTW - Even if the form displays "Don't
click the mouse while this is working" the users still do and crash the
program).

Turned the Pop Up and Modal attributes to No.

Better indexed my data.

Enabled the "Raise execution priority from Windows applications" option
in SQL Server.

Thanks in advance. Any help would be greatly appreciated.

Oct 24 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
If the process is part of a loop, you could use the DoEvents function
to allow the operating system to process the mouse click events. If
this isn't possible, perhaps if you posted the process code here, a
solution could be found. If you'd like, you could even email to me and
I'll see if I can see anything that might help.
Typehigh wrote:
I am front ending a SQL Server database with MS-Access 2000. The UI has
many buttons that launch VB code. One of the buttons launches a lengthy
process that takes 20-30 seconds to complete. If the user starts
clicking their mouse off of the active window the Access Toolbar
displays Microsoft Access (Not Responding) and then moments later a
hard crash occurs and is announced by a system dialog box. When the
user clicks the OK button in the dialog box Access terminates and needs
to be restarted.

Things I've tried:

Popping up a form announcing "Processing". The form has both Pop Up and
Modal attributes set to Yes. (BTW - Even if the form displays "Don't
click the mouse while this is working" the users still do and crash the
program).

Turned the Pop Up and Modal attributes to No.

Better indexed my data.

Enabled the "Raise execution priority from Windows applications" option
in SQL Server.

Thanks in advance. Any help would be greatly appreciated.
Oct 24 '06 #2

P: n/a
Brian,

I tried it, but the program still crashes hard.
It's the Access version of the BSOD (Blue Screen Of Death)

Neil

Brian Puffer wrote:
If the process is part of a loop, you could use the DoEvents function
to allow the operating system to process the mouse click events. If
this isn't possible, perhaps if you posted the process code here, a
solution could be found. If you'd like, you could even email to me and
I'll see if I can see anything that might help.
Typehigh wrote:
I am front ending a SQL Server database with MS-Access 2000. The UI has
many buttons that launch VB code. One of the buttons launches a lengthy
process that takes 20-30 seconds to complete. If the user starts
clicking their mouse off of the active window the Access Toolbar
displays Microsoft Access (Not Responding) and then moments later a
hard crash occurs and is announced by a system dialog box. When the
user clicks the OK button in the dialog box Access terminates and needs
to be restarted.

Things I've tried:

Popping up a form announcing "Processing". The form has both Pop Up and
Modal attributes set to Yes. (BTW - Even if the form displays "Don't
click the mouse while this is working" the users still do and crash the
program).

Turned the Pop Up and Modal attributes to No.

Better indexed my data.

Enabled the "Raise execution priority from Windows applications" option
in SQL Server.

Thanks in advance. Any help would be greatly appreciated.
Oct 27 '06 #3

P: n/a
Brian,

Thanks for the tip, it got me thinking and trying new things.

I got the code to work using DoEvents and here is how I did it:

FOR intX = 1 TO SomeLargeNumber
code
code
code
code
IF intX MOD 200 = 0 THEN
DoEvents
END IF
NEXT

The reason I did it this way is because DoEvents will slow a loop down,
so I only evoke it every 200 loop cycles.

Thanks again,

Neil
Typehigh wrote:
Brian,

I tried it, but the program still crashes hard.
It's the Access version of the BSOD (Blue Screen Of Death)

Neil

Brian Puffer wrote:
If the process is part of a loop, you could use the DoEvents function
to allow the operating system to process the mouse click events. If
this isn't possible, perhaps if you posted the process code here, a
solution could be found. If you'd like, you could even email to me and
I'll see if I can see anything that might help.
Typehigh wrote:
I am front ending a SQL Server database with MS-Access 2000. The UI has
many buttons that launch VB code. One of the buttons launches a lengthy
process that takes 20-30 seconds to complete. If the user starts
clicking their mouse off of the active window the Access Toolbar
displays Microsoft Access (Not Responding) and then moments later a
hard crash occurs and is announced by a system dialog box. When the
user clicks the OK button in the dialog box Access terminates and needs
to be restarted.
>
Things I've tried:
>
Popping up a form announcing "Processing". The form has both Pop Up and
Modal attributes set to Yes. (BTW - Even if the form displays "Don't
click the mouse while this is working" the users still do and crash the
program).
>
Turned the Pop Up and Modal attributes to No.
>
Better indexed my data.
>
Enabled the "Raise execution priority from Windows applications" option
in SQL Server.
>
Thanks in advance. Any help would be greatly appreciated.
Nov 2 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.