[AccessD] Microsoft Access Has Stopped Working

Hi Rocky

It was a combobox where the doubleclick event called a sub that returned byref an array which another function used to rebuild the value list of the combobox. It seemed to work but some seconds later Access crashed.

I changed it by creating a copy of the array, passing this (still byref) to the sub, and then copy the revised array to replace the original before calling the function that rebuild the value list. No crash after this.

/gustav


>>> rockysmolin at bchacc.com 03-08-12 0:27 >>>
Gustav:

My user is still reporting the problem - every time he deletes a sales
order. Seems consistent and for him, delaying a couple of seconds before
clicking OK to the last message ("Sales Order Deleted.") doesn't seem to
help.

What kind of changes to the code did you do? 

TIA

Rocky


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Tuesday, July 31, 2012 1:56 PM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Microsoft Access Has Stopped Working

Hi Rocky

I've seen it with A2010 when doing naughty things, repeatable * changed the
code and it was gone. And occasionally for "no" reason.
As you suggest - could be a timing issue. But, I think, outside our control.

/gustav


>>> rockysmolin at bchacc.com 31-07-12 21:20 >>>
Dear List:
 
How I HATE that message.  Suddenly, for no apparent reason and making no
excuses, Access stop working and give you only the curt message 'Microsoft
Access has stopped working." and bails, leaving the ldb files open, as well
as my mouth in disbelief.  Not even a clue why.  But I digress.
 
Yesterday I ran into this twice on an app that HAS been working.  I can go
into the details later if necessary.
 
But the first case I was able to duplicate here - has to do with deleting a
record (SO Header), which cascade deletes child record (SO Detail), and then
displays a MsgBox "Sales Order Deleted" and user clicks OK.  If I wait a
couple of seconds and click OK, no problem.  If I click OK real fast,
Microsoft Access stops working!  I tried inserting a DoEvents before that
last MsgBox - no seegar. Tried a subroutine to delay x milliseconds, it blew
up on the call to that routine.
 
So I think there's some kind of timing problem there.  Maybe.
 
The second case involves a form which displays PO details.  Double-clicking
on the PO Number opens the PO form and displays the whole PO.  Clicking exit
closes the form and you return to the first form.  Works like a champ here.
User says when they click Exit in the Purchase Order form...Microsoft Access
stops working!
 
Does anyone have any insight into this?  Seen it before?  Know how to fix
it?
 
MMTIA