What the hell is this: run-time error '-2146500594 (800f000e)'

[NB]

Hi

In my 2 years with Access I have never seen this, now it makes me mad

In an unbound form frmTH I have a frmList which is a continous form
In its on current event, I synch 4 of its fields with 4 unbound
textboxes on the parent form

Me.parent!txtLink1 = Me!field1
Me.parent!txtLink2 = Me!field2

I've been doing this for ages with many apps

And here comes the f***ing error when I run the form:

run-time error '-2146500594 (800f000e)':
Method 'Parent' of object '_Form_frmTHList' failed

I created a totally new unbound form frmTH with the unbound textboxes,
a new frmList and it still comes. I compact and repair the mdb, it's
still there.
I created a blank mdb and import all object into it: import process is
smooth, no error. And the damn error is there.

I even synch using these in the on current event
Forms!frmTH!txtLink1 = Me!field1
Forms!frmTH!txtLink2 = Me!field2
......

and it becomes:
run-time error '-2146500594 (800f000e)':
Method 'Item' of object 'Forms' failed

Other apps with the same synching mechanism still run fine on my PC
(Win XP, Access 2002).

Any suggestion? work-around to synch a continuous subform with other
subform not using the oncurrent event method?

Thks very much
NB

[Steve Jorgensen]

As you have probably experienced, there are many times when Access fails to
report a meaningful error message for a simple problem, and this is probably
one of them. I'm thinking either the control is bound to a misspelled field
name or you calling the code from somewhere prior to when the form's
recordsource has been fully initialized (a frequent problem in OnCurrent
handlers).

On 29 Dec 2003 03:24:39 -0800, ni******@lycos.com (NB) wrote:

Hi

In my 2 years with Access I have never seen this, now it makes me mad

In an unbound form frmTH I have a frmList which is a continous form
In its on current event, I synch 4 of its fields with 4 unbound
textboxes on the parent form

Me.parent!txtLink1 = Me!field1
Me.parent!txtLink2 = Me!field2

I've been doing this for ages with many apps

And here comes the f***ing error when I run the form:

run-time error '-2146500594 (800f000e)':
Method 'Parent' of object '_Form_frmTHList' failed

I created a totally new unbound form frmTH with the unbound textboxes,
a new frmList and it still comes. I compact and repair the mdb, it's
still there.
I created a blank mdb and import all object into it: import process is
smooth, no error. And the damn error is there.

I even synch using these in the on current event
Forms!frmTH!txtLink1 = Me!field1
Forms!frmTH!txtLink2 = Me!field2
.....

and it becomes:
run-time error '-2146500594 (800f000e)':
Method 'Item' of object 'Forms' failed

Other apps with the same synching mechanism still run fine on my PC
(Win XP, Access 2002).

Any suggestion? work-around to synch a continuous subform with other
subform not using the oncurrent event method?

Thks very much
NB

[Tom van Stiphout]

On 29 Dec 2003 03:24:39 -0800, ni******@lycos.com (NB) wrote:

Check your references. Is one missing or out of order?
-Tom.

Hi

In my 2 years with Access I have never seen this, now it makes me mad

In an unbound form frmTH I have a frmList which is a continous form
In its on current event, I synch 4 of its fields with 4 unbound
textboxes on the parent form

Me.parent!txtLink1 = Me!field1
Me.parent!txtLink2 = Me!field2

I've been doing this for ages with many apps

And here comes the f***ing error when I run the form:

run-time error '-2146500594 (800f000e)':
Method 'Parent' of object '_Form_frmTHList' failed

I created a totally new unbound form frmTH with the unbound textboxes,
a new frmList and it still comes. I compact and repair the mdb, it's
still there.
I created a blank mdb and import all object into it: import process is
smooth, no error. And the damn error is there.

I even synch using these in the on current event
Forms!frmTH!txtLink1 = Me!field1
Forms!frmTH!txtLink2 = Me!field2
.....

and it becomes:
run-time error '-2146500594 (800f000e)':
Method 'Item' of object 'Forms' failed

Other apps with the same synching mechanism still run fine on my PC
(Win XP, Access 2002).

Any suggestion? work-around to synch a continuous subform with other
subform not using the oncurrent event method?

Thks very much
NB

[NB]

I forgot to mention 1 important detail

All the synching worked perfectly normal (hence your suggestions are
all wrong)
until I put some code on the On Exit event of the control that holds
the continuous list subform, or on the On Enter event of another
subform on the same form

If I revert the form to the stage before adding those On Enter and On
Exit events then everything is fine

If I save the form, then remove the OnEnter and On Exit event codes:
the damn error persists and I have to create a new form.

So....
This is very mysterious, and no explanation found yet

I have to accept this, and managed to find a workaround that
accomplish what I want without the On Enter and On Exit events

Thks guys for trying anyway

NB

[LesM]

I too have recently suffered this error using Access2000 (both SR-1 and
SP3). I haven't yet found the cause or cure, but can contribute some
additional details that may help someone.
The difference with my system is that the error occurred on a system
that has been working perfectly well since 16 Dec 03. Then suddenly on
8th Jan 04 having been in use for 6 hours that day, the user clicked on
the button on my main menu form, that opens another form with several
subforms, and the error occurred. But this button has been clicked
successfully dozens of times in exactly the same circumstances since the
program was released on 16 Dec. Now it crashes every time.
My system consists of two DBs, one containing all the forms and code
which is linked to the other containing all the data tables.
I copied my development version of the forms & Code program (which has
had no changes since 16 Dec)across to live and it work OK.
So from this we can deduce that the error can occur in a previously
working program without any changes to forms or code.
As the error occurs in the Form_Current of the subform, it probably is a
timing issue relating to the forms not completing their initialisation
before the code executes, as suggested by someone else. What I can't
explain is why it has suddenly changed and now consistently crashes.

LesM

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Sebastian]

Les, Have you figured out what was causing the problem?
I am working on a database which consists, basically, of a form with
many subforms. Through the use of buttons, I turn the subforms
visible/invisible and do all the processing I need.
I was modifying the design of one of the sub-forms (height/width), and
when I tried to open the container in normal vie, I got this freaking
error you mentioned, except that the message reads:
Method 'Item' of object 'Forms' failed
Any ideas??
Thanks!!