Drill down Fails with access 2003

  • Thread starter Thread starter GlynnSmith
  • Start date Start date
G

GlynnSmith

I have an application that uses a drill down from subform
and a field of the subform is used to select the record to
display at the lower level. This works just fine with
access from office 2000, but fails with access from office
2003. The problem appears to be that the subform field is
not risible at the lowe level so the form comes up blank
instead of selecting the proper record.
 
GlynnSmith said:
I have an application that uses a drill down from subform
and a field of the subform is used to select the record to
display at the lower level. This works just fine with
access from office 2000, but fails with access from office
2003. The problem appears to be that the subform field is
not risible at the lowe level so the form comes up blank
instead of selecting the proper record.
Click to expand...

Could you post the code and give more details? I don't have Access
2003, but I might notice something. Have you checked your references to
make sure a broken reference isn't behind the odd behavior?
 
How do I check references?

Sample drilldown code.

[ProductSerialNoID]=[Forms]![Order Detail]![Product
Subform]![ProductSerialNoID]
 
Glynn Smith said:
How do I check references?

Sample drilldown code.

[ProductSerialNoID]=[Forms]![Order Detail]![Product
Subform]![ProductSerialNoID]

-----Original Message-----


Could you post the code and give more details? I don't have Access
2003, but I might notice something. Have you checked your
references to make sure a broken reference isn't behind the odd
behavior?
Click to expand...
Click to expand...

Please post more of the surrounding code, preferably the entire event
procedure, to put the code in context.

To check for broken references, go to the VB Editor environment, click
Tools -> References..., and look for any reference marked as MISSING.
Note that some reference problems aren't immediately flagged, so if you
don't see one so marked but suspect a reference problem anyway, you can
try this: note down the name of some checked reference, un-check it,
close the dialog, open the dialog again, locate the reference (it will
probably have moved), and check it again.

Another thing to check, since a subform reference is involved, is the
Name AutoCorrect option. In the main Access window, click Tools ->
Options..., go to the General tab, and see if Track name AutoCorrect is
switched on. If it is, try turning it off and see if your problem goes
away.
 
-----Original Message-----
How do I check references?

Sample drilldown code.

[ProductSerialNoID]=[Forms]![Order Detail]![Product
Subform]![ProductSerialNoID]

-----Original Message-----
I have an application that uses a drill down from subform
and a field of the subform is used to select the record to
display at the lower level. This works just fine with
access from office 2000, but fails with access from office
2003. The problem appears to be that the subform field is
not risible at the lowe level so the form comes up blank
instead of selecting the proper record.

Could you post the code and give more details? I don't have Access
2003, but I might notice something. Have you checked your
references to make sure a broken reference isn't behind the odd
behavior?
Click to expand...
Click to expand...

Please post more of the surrounding code, preferably the entire event
procedure, to put the code in context.
Click to expand...

On the subform I have a Command Box with the "Event On
Click" defined as "Drill Down.OrderToProduct".

The drill down macro named OrderToProduct has an action of
OpenForm. The form name is ProductDetail and the Where
Condition is defined as [ProductSerialNoID]=[Forms]![Order
Detail]![Product Subform]![ProductSerialNoID]

Where ProductSerialNoID is a valid element on the Product
Subform display.

Remember, this all works fine on 2000 but fails on 2003.

would it be helpfull if I emailed the entire application
to you.
To check for broken references, go to the VB Editor environment, click
Tools -> References..., and look for any reference marked as MISSING.
Note that some reference problems aren't immediately flagged, so if you
don't see one so marked but suspect a reference problem anyway, you can
try this: note down the name of some checked reference, un-check it,
close the dialog, open the dialog again, locate the reference (it will
probably have moved), and check it again.

Another thing to check, since a subform reference is involved, is the
Name AutoCorrect option. In the main Access window, click Tools ->
Options..., go to the General tab, and see if Track name AutoCorrect is
switched on. If it is, try turning it off and see if your problem goes
away.
Click to expand...

I did switch off Track name AutoCorrect and this had no
effect.
 
Glynn Smith said:
-----Original Message-----
Glynn Smith said:
How do I check references?

Sample drilldown code.

[ProductSerialNoID]=[Forms]![Order Detail]![Product
Subform]![ProductSerialNoID]


-----Original Message-----
I have an application that uses a drill down from subform
and a field of the subform is used to select the record to
display at the lower level. This works just fine with
access from office 2000, but fails with access from office
2003. The problem appears to be that the subform field is
not risible at the lowe level so the form comes up blank
instead of selecting the proper record.

Could you post the code and give more details? I don't have Access
2003, but I might notice something. Have you checked your
references to make sure a broken reference isn't behind the odd
behavior?
Click to expand...

Please post more of the surrounding code, preferably the entire event
procedure, to put the code in context.
Click to expand...

On the subform I have a Command Box with the "Event On
Click" defined as "Drill Down.OrderToProduct".

The drill down macro named OrderToProduct has an action of
OpenForm. The form name is ProductDetail and the Where
Condition is defined as [ProductSerialNoID]=[Forms]![Order
Detail]![Product Subform]![ProductSerialNoID]

Where ProductSerialNoID is a valid element on the Product
Subform display.
Click to expand...

Oh, so this is a macro, not VBA code at all. I hadn't understood that
before -- the fact that your post is in the formscoding newsgroup misled
me. I'm not even all that familiar with macros, as I don't use them,
but it doesn't really make sense that the problem should be with the
macro itself.

Does it help if you change the macro action's Where Condition to

[ProductSerialNoID]=[Forms]![Order Detail]![Product
Subform].[Form]![ProductSerialNoID]

? (See where I've inserted the ".[Form]" qualifier?) I wouldn't expect
that to be necessary, but I've heard that Access 2003 is pickier about
some object references than earlier versions.
would it be helpfull if I emailed the entire application
to you.
Click to expand...

Unfortunately, I don't have Access 2003 installed on any PC, so I don't
think that would help unless the application also fails on Access 2002.

Have you made absolutely sure that "Product Subform" is the name of the
subform control on form "Order Detail"?
 
(resending because original message doesn't appear)

Glynn Smith said:
-----Original Message-----
Glynn Smith said:
How do I check references?

Sample drilldown code.

[ProductSerialNoID]=[Forms]![Order Detail]![Product
Subform]![ProductSerialNoID]


-----Original Message-----
I have an application that uses a drill down from subform
and a field of the subform is used to select the record to
display at the lower level. This works just fine with
access from office 2000, but fails with access from office
2003. The problem appears to be that the subform field is
not risible at the lowe level so the form comes up blank
instead of selecting the proper record.

Could you post the code and give more details? I don't have Access
2003, but I might notice something. Have you checked your
references to make sure a broken reference isn't behind the odd
behavior?
Click to expand...

Please post more of the surrounding code, preferably the entire event
procedure, to put the code in context.
Click to expand...

On the subform I have a Command Box with the "Event On
Click" defined as "Drill Down.OrderToProduct".

The drill down macro named OrderToProduct has an action of
OpenForm. The form name is ProductDetail and the Where
Condition is defined as [ProductSerialNoID]=[Forms]![Order
Detail]![Product Subform]![ProductSerialNoID]

Where ProductSerialNoID is a valid element on the Product
Subform display.
Click to expand...

Oh, so this is a macro, not VBA code at all. I hadn't understood that
before -- the fact that your post is in the formscoding newsgroup misled
me. I'm not even all that familiar with macros, as I don't use them,
but it doesn't really make sense that the problem should be with the
macro itself.

Does it help if you change the macro action's Where Condition to

[ProductSerialNoID]=[Forms]![Order Detail]![Product
Subform].[Form]![ProductSerialNoID]

? (See where I've inserted the ".[Form]" qualifier?) I wouldn't expect
that to be necessary, but I've heard that Access 2003 is pickier about
some object references than earlier versions.
would it be helpfull if I emailed the entire application
to you.
Click to expand...

Unfortunately, I don't have Access 2003 installed on any PC, so I don't
think that would help unless the application also fails on Access 2002.

Have you made absolutely sure that "Product Subform" is the name of the
subform control on form "Order Detail"?
 
-----Original Message-----
(resending because original message doesn't appear)

-----Original Message-----
How do I check references?

Sample drilldown code.

[ProductSerialNoID]=[Forms]![Order Detail]![Product
Subform]![ProductSerialNoID]


-----Original Message-----
I have an application that uses a drill down from subform
and a field of the subform is used to select the record to
display at the lower level. This works just fine with
access from office 2000, but fails with access from office
2003. The problem appears to be that the subform field is
not risible at the lowe level so the form comes up blank
instead of selecting the proper record.

Could you post the code and give more details? I don't have Access
2003, but I might notice something. Have you checked your
references to make sure a broken reference isn't behind the odd
behavior?

Please post more of the surrounding code, preferably the entire event
procedure, to put the code in context.
Click to expand...

On the subform I have a Command Box with the "Event On
Click" defined as "Drill Down.OrderToProduct".

The drill down macro named OrderToProduct has an action of
OpenForm. The form name is ProductDetail and the Where
Condition is defined as [ProductSerialNoID]=[Forms]! [Order
Detail]![Product Subform]![ProductSerialNoID]

Where ProductSerialNoID is a valid element on the Product
Subform display.
Click to expand...

Oh, so this is a macro, not VBA code at all. I hadn't understood that
before -- the fact that your post is in the formscoding newsgroup misled
me. I'm not even all that familiar with macros, as I don't use them,
but it doesn't really make sense that the problem should be with the
macro itself.

Does it help if you change the macro action's Where Condition to

[ProductSerialNoID]=[Forms]![Order Detail]![Product
Subform].[Form]![ProductSerialNoID]

? (See where I've inserted the ".[Form]" qualifier?) I wouldn't expect
that to be necessary, but I've heard that Access 2003 is pickier about
some object references than earlier versions.
Click to expand...
This is it!!! inserting the .[Form] fixed the problem.
Thanks a lot for your help.
 
Back
Top