Access 2000 app not working on winxp

[John]

Hi

I have an access app that runs fine on access 2000 on a windows 2000 pc. I
installed access 2000 on a second win xp pro pc with ms office xp small
business already installed. When I run the app on this pc and try to
add/delete records and then move around I get an 'Object invalid or not set'
error. The offending line is me.requery. me in this case is a form that
contains a couple of subforms. Any ideas what the problem is? Could it be a
conflict between access 2000 and office xp small business or may be win xp
pro?

Thanks

Regards

[Pavel Romashkin]

I would guess, a missing reference and nothing to do with the OS.

Pavel

John wrote:

Hi

I have an access app that runs fine on access 2000 on a windows 2000 pc. I
installed access 2000 on a second win xp pro pc with ms office xp small
business already installed. When I run the app on this pc and try to
add/delete records and then move around I get an 'Object invalid or not set'
error. The offending line is me.requery. me in this case is a form that
contains a couple of subforms. Any ideas what the problem is? Could it be a
conflict between access 2000 and office xp small business or may be win xp
pro?

Thanks

Regards

[John]

The form opens fine the first time. When I move to second tab and delete or
add a record on the sub form and then switch back to first tab I get the
error. This problem is only on two winxp/officexp sb machines. Both machines
are brand new. No error comes on win2000/office2000 machines. If after
adding a record on second tab I quit access and then open the form again on
the first tab no error. It has something to do with adding/deleting records
on a subform on tab 2. Not sure what. Could it be a DAO issue?

Thanks

Regards

"Pavel Romashkin" <pa*************@hotmail.com> wrote in message
news:3F***************@hotmail.com...

I would guess, a missing reference and nothing to do with the OS.

Pavel

John wrote:

Hi

I have an access app that runs fine on access 2000 on a windows 2000 pc. I installed access 2000 on a second win xp pro pc with ms office xp small
business already installed. When I run the app on this pc and try to
add/delete records and then move around I get an 'Object invalid or not set' error. The offending line is me.requery. me in this case is a form that
contains a couple of subforms. Any ideas what the problem is? Could it be a conflict between access 2000 and office xp small business or may be win xp pro?

Thanks

Regards

[Pavel Romashkin]

It is difficult to provide a solution based on such a general
description. Are the forms using code or just purely bound? One thing
you may want to try is, look at the references. What is the order of
references? Is DAO referenced? Is it bafore or after ADO? Are Recordset
objects defined explicitly?
Lines like

Dim Rst as Recordset

are the typical cause of grief becasuse ADO is usually referenced first
in newer installations, and developers assumed DAO when Rst was defined.

Pavel

John wrote:

The form opens fine the first time. When I move to second tab and delete or
add a record on the sub form and then switch back to first tab I get the
error. This problem is only on two winxp/officexp sb machines. Both machines
are brand new. No error comes on win2000/office2000 machines. If after
adding a record on second tab I quit access and then open the form again on
the first tab no error. It has something to do with adding/deleting records
on a subform on tab 2. Not sure what. Could it be a DAO issue?

Thanks

Regards

"Pavel Romashkin" <pa*************@hotmail.com> wrote in message
news:3F***************@hotmail.com...

I would guess, a missing reference and nothing to do with the OS.

Pavel

John wrote:

Hi

I have an access app that runs fine on access 2000 on a windows 2000 pc. I installed access 2000 on a second win xp pro pc with ms office xp small
business already installed. When I run the app on this pc and try to
add/delete records and then move around I get an 'Object invalid or not set' error. The offending line is me.requery. me in this case is a form that
contains a couple of subforms. Any ideas what the problem is? Could it be a conflict between access 2000 and office xp small business or may be win xp pro?

Thanks

Regards