M
Myron Oakley
I have a very mature and well debugged Access 97 application I recently
converted to Access 2000. Everything initially appeared fine until we tried
to add a new record using our "Add New" buttons on some our forms. Some
worked fine, some crashed with the Run Time Error 3426, This action was
cancelled by an associated object. This was driving me nuts as the VBA code
was exactly the same on forms that worked also. This would always crash at
rstClone.addnew. I finally found the difference, stumbled on it I guess,
it was on the form and not the VBA! The crashing forms had drop down combo
boxes bound to fields in the record.
So.....
I deleted the combos on an offending form, and it added the new record
without crashing. The big problem is: I NEED THOSE COMBO BOXES. The seems
like one hell of a bug in Access 2000 as far as migration is concerned. Has
anyone found a work around for this?
TIA
Myron Oakley
PCM
converted to Access 2000. Everything initially appeared fine until we tried
to add a new record using our "Add New" buttons on some our forms. Some
worked fine, some crashed with the Run Time Error 3426, This action was
cancelled by an associated object. This was driving me nuts as the VBA code
was exactly the same on forms that worked also. This would always crash at
rstClone.addnew. I finally found the difference, stumbled on it I guess,
it was on the form and not the VBA! The crashing forms had drop down combo
boxes bound to fields in the record.
So.....
I deleted the combos on an offending form, and it added the new record
without crashing. The big problem is: I NEED THOSE COMBO BOXES. The seems
like one hell of a bug in Access 2000 as far as migration is concerned. Has
anyone found a work around for this?
TIA
Myron Oakley
PCM