IPF Error after simple form change

  • Thread starter Thread starter ZRexRider
  • Start date Start date
Z

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
 
This behavior for A2002 has been reported many times in the past since the
introduction of SP2 for Windows, I think and has nothing to do with the
conversion from A2003 to A2002. I don't know of any specific solution to
this and in fact, this is the reason for my own switch from A2002 to A2003.

You can try creating an empty database on a machine with A2002 and import
everything into it, to make sure that everything is up to date; however I
seriously doubt if this will correct the situation.

Otherwise, your only solution might be to use an unbound field and to
manually update its value when entering and leaving a record (won't work
with continuous forms) or replace either the checkbox of the bit field with
something else.
 
Thanks - I tried creating an empty A2002 and imported all in but still
bad. Don't have the option of getting the customer up on 2003 (big
enterprise). Don't have A2002 for my own offsite workstation.

I'll try adding a cmd button and if clicked I will set the bit. 'Tis
no fun let me tell you!

FYI if I open the error report I find the the mod is ADO.

AppName: msaccess.exe AppVer: 10.0.6501.0 ModName: msado15.dll
ModVer: 2.71.9030.0 Offset: 0004537d
 
Making this even odder:

If I add the following code behind an existing button (for a quick
test)

Me.bitReviewed.Value = True

Works fine w/o any error and updates the database.

However, if I add a new cmd button to this form and put the same code
behind it, Access dies when I click it. Seems to be a combination of
both.
 
Yeah, this looks like some sort of memory corruption problem; so it will
work, don't work, works again, .... Making a slight change make change
everything; however, when it's start bombing, the most outcomes is that it
will keep bombing. Someone has even called it "the small change of death".

Try replacing the Bit field with a tiny or an int field; close/reopen the
project, recompile everything and see what happens.
 
Thanks for your ideas... I had to give up.

My horrible solution (based on deadline) was to put SQL update
statement behind this new unbound checkbox. I tried everything short
of creating this relatively complicated form from scratch. That
probably would have worked but to high a price to pay. I put a nice 10
line comment banner on the event routine explaining why I was doing
such an odd update.

MS-Access can make you crazy sometimes.
 
I'm not sure if it's necessary to put a SQL update behind the unbound
checkbox: maybe simply changing the field in the current record will work.
All you have to do is to bound the others fields of the underlying recordset
but not this one.

Maybe it's time for your clients to upgrade to A2003. However, with the
forthcoming Access 2006, this might not be the best time to upgrade; excerpt
if your clients are willing to wait at least for the first SP1 to A2006
before upgrading.
 
Thanks - client is huge and has their own reason for not rolling out
latest Access so I'm kind of stuck there. Probably I should find a
copy of Access 2002 and get in synch with them and be done with it.

How do I learn about what might be coming in Access 2006

Thanks again
 
Acccess 2006 and ADP? Probably nothing new: same old bits excerpt for the
colors of the menus.
 
Back
Top