Catastrophic Access crash

[ZRexRider]

Hi,


I have an ADP file created in MS-Access 2003 SP1 that is working very
well. Unfortunately I have to deploy on workstations having MS-Access
2002 SP3.


I have rarely experienced a problem with this risky behavior but today
I think it has caught up with me.


On my development box (Access 2003) I added a simple check box to a
form. It's bound to a SQL server field (within a recordset). Works
great with no surprises.


I copy this same ADP file to the MS-Access 2002 machine and 99% of the
program works as expected - except when I click that new check box.
That check box is like a detonator for a nuclear strike. As soon as
it's clicked, MS-Access commits suicide.


I've opened the app in dev mode and used menu options (Debug|Compile)
and tried again and got same results.


I've tried starting the App by using the /Decompile switch and got the
same results.


I've delete the check box and added it back while on the MS-Access 2002

machine and got the same results.


I'm about to create a new form and scrape all of the objects and code
onto it to see if I can recover this way.


Anybody have any better ideas?


Thanks

 

[Tony Toews]

On my development box (Access 2003) I added a simple check box to a
form. It's bound to a SQL server field (within a recordset). Works
great with no surprises.


I copy this same ADP file to the MS-Access 2002 machine and 99% of the
program works as expected - except when I click that new check box.
That check box is like a detonator for a nuclear strike. As soon as
it's clicked, MS-Access commits suicide.

I vaguely recall someone reporting this as a problem recently.
Possibly there is an article on this problem on the Knowledge Base at
support.microsoft.com. (I'm on a dialup right now otherwise I'd
search it myself.)

Now is that check box defined as a triple state? If so that won't
work against a boolean field.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[ZRexRider]

You might have something there. I will check the "triple-state" factor
when i get back to the office. Although I think we both agree that
nuclear destruction is not an appropriate response to bad programming
;-)

To get out from under this "problem" I had to unbind the control and
code an UPDATE statement behind the click event - yuck!

Thanks

 

[Tony Toews]

You might have something there. I will check the "triple-state" factor
when i get back to the office. Although I think we both agree that
nuclear destruction is not an appropriate response to bad programming
;-)

<chuckle> Agreed.

In Microsoft's defense they really, really like those crash reports
that folks send off to them. Solving crashing problems for the next
Service Pack is a very high priority. Now they don't like getting
those in the first place.

So please send those in as much as possible.

The funniest comment was from a Microsoft employee lamenting about how
his mom was ragging on him for something that was crashing.

To get out from under this "problem" I had to unbind the control and
code an UPDATE statement behind the click event - yuck!

<understatement>Not an ideal solution. </understatement>

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm