Object invalid error in Acc 2002

[Owen Jenkins]

I have found references to this problem in several threads on this
newsgroup but none provide an answer to explain this problem. So any
further assistance would be very helpful...

I have 2 forms (one in form view-FF, one in datasheet view-FD) which are
open together and which use a query as the recordsource with data from
the same table. When one form (FF) is visible, the other (FD) is hidden.
In some circumstances, entering data onto the FF form gives an 'object
invalid or no longer set' error. When I look at the datasheet form FD,
all the records show #NAME. Any other keystrokes cause repeated object
invalid ... errors which cannot be trapped in the running code. Data can
be entered into the FF OK, but when data is entered into a linked
subform on the FF form, the FD form loses it's recordset.

I understand there may be issues with basing two forms on the same
table, but this can't be the entire answer. The reasons being ...
1. The app has been working now for 120 clients for 4 years.
2. The app works in Acc97 on the same computer on which it doesn't work
in Acc2002.
3. The app works one one computer with a similar configuration as one
where it doesn't work.

Specifially, the app (mde) is written in A97 and converted to A2000 for
clients with A2000/2002. The rogue machine has Access 2002 and Win XP
home. I have checked the references and all are OK. I have
uninstalled/reinstalled my app and Office XP. It happens with mde or
mdb. When I run the A97 version on the same machine with the Acc97
runtime, the app works fine.

Mysterious eh. Is it a M$ issue?

Owen Jenkins
[e-mail]

[TC]

Well, if you showed the lines of code that got the error, someone could
doubtless tell you the cause!

TC
"Owen Jenkins" <[e-mail]> wrote in message
news:3F**************@healthbase.com.au...

I have found references to this problem in several threads on this
newsgroup but none provide an answer to explain this problem. So any
further assistance would be very helpful...

I have 2 forms (one in form view-FF, one in datasheet view-FD) which are
open together and which use a query as the recordsource with data from
the same table. When one form (FF) is visible, the other (FD) is hidden.
In some circumstances, entering data onto the FF form gives an 'object
invalid or no longer set' error. When I look at the datasheet form FD,
all the records show #NAME. Any other keystrokes cause repeated object
invalid ... errors which cannot be trapped in the running code. Data can
be entered into the FF OK, but when data is entered into a linked
subform on the FF form, the FD form loses it's recordset.

I understand there may be issues with basing two forms on the same
table, but this can't be the entire answer. The reasons being ...
1. The app has been working now for 120 clients for 4 years.
2. The app works in Acc97 on the same computer on which it doesn't work
in Acc2002.
3. The app works one one computer with a similar configuration as one
where it doesn't work.

Specifially, the app (mde) is written in A97 and converted to A2000 for
clients with A2000/2002. The rogue machine has Access 2002 and Win XP
home. I have checked the references and all are OK. I have
uninstalled/reinstalled my app and Office XP. It happens with mde or
mdb. When I run the A97 version on the same machine with the Acc97
runtime, the app works fine.

Mysterious eh. Is it a M$ issue?

Owen Jenkins
[e-mail]