Random Access 2000 Crashes (ADO Fault)

[Adam Goossens]

Hi folks,

Forgive me if this question has been asked before.

I am currently working on an ADP for a client and have it about 90%
complete. It needs to be production ready quite soon (the client has
already been waiting at least a month). However, I am being consistently
plagued by what appear to be totally random Access crashes.

By digging through the Event Log I discovered that I am getting
consistent ADO faults which are causing the MSACCESS process to be shut
down. (stupid me forgot to note down the exact error though - I'll
attempt to reproduce the fault again). I've tried altering the
references to the latest version of ADO installed (from 2.1 to 2.7) to
no avail.

As you can imagine, this is not the best thing for a client to see when
they test drive your application

The crashes appear to be completely random, and occur from things like this:

---
DoCmd.RunCommand acCmdSaveRecord << crash here.
Me.cboTool.Requery
---

Or this:

---
Me.txtJobNo = iJobNo
---

(txtJobNo is a bound control)

Has anybody ever run into something like this before, and if so were you
able to resolve it? I guess it goes without saying that this is
extraordinarily frustrating - everything is working perfectly and then a
seemingly innocuous statement causes it all to go pear shaped

The strangest thing is that whilst I do get faults at the workplace,
they are far more frequent at the client. Or is that called Murphy's Law?

If you need any more information let me know, and you'll have anything
you need.

Thanks for any help!

Regards,
-Adam Goossens

 

[Tom Wickerath]

Hi Adam,

If you suspect an ADO fault, it might be worth your time to download the
MDAC Component checker utility and run it on all PC's.

Component Checker: Diagnose problems and reconfigure MDAC installations
http://support.microsoft.com/?id=307255

Tom
____________________________________

:

Hi folks,

Forgive me if this question has been asked before.

I am currently working on an ADP for a client and have it about 90%
complete. It needs to be production ready quite soon (the client has
already been waiting at least a month). However, I am being consistently
plagued by what appear to be totally random Access crashes.

By digging through the Event Log I discovered that I am getting
consistent ADO faults which are causing the MSACCESS process to be shut
down. (stupid me forgot to note down the exact error though - I'll
attempt to reproduce the fault again). I've tried altering the
references to the latest version of ADO installed (from 2.1 to 2.7) to
no avail.

As you can imagine, this is not the best thing for a client to see when
they test drive your application

The crashes appear to be completely random, and occur from things like this:

---
DoCmd.RunCommand acCmdSaveRecord << crash here.
Me.cboTool.Requery
---

Or this:

---
Me.txtJobNo = iJobNo
---

(txtJobNo is a bound control)

Has anybody ever run into something like this before, and if so were you
able to resolve it? I guess it goes without saying that this is
extraordinarily frustrating - everything is working perfectly and then a
seemingly innocuous statement causes it all to go pear shaped

The strangest thing is that whilst I do get faults at the workplace,
they are far more frequent at the client. Or is that called Murphy's Law?

If you need any more information let me know, and you'll have anything
you need.

Thanks for any help!

Regards,
-Adam Goossens