Conditional Formatting Cause Running Sum Error

Any ideas about why adding a conditional format would cause a running
sum control to display "#Name?" instead of the running sum value?
Without conditional formatting, it works fine.

Condition statement: [IS_PLACEHOLDER]

Note: IS_PLACEHOLDER is a Yes/No field in the underlying query.

Thanks!

Make sure you don't have a control with the same name on the report. #Name
indicates that Access is confused: it either can't find it or doesn't know
which one you want (feast or famine).

HTH,

"Tom" wrote in message
oups.com...
Any ideas about why adding a conditional format would cause a running
sum control to display "#Name?" instead of the running sum value?
Without conditional formatting, it works fine.

Condition statement: [IS_PLACEHOLDER]

Note: IS_PLACEHOLDER is a Yes/No field in the underlying query.

Thanks!

On Aug 2, 10:54 am, "George Nicholson"
wrote:
Make sure you don't have a control with the same name on the report. #Name
indicates that Access is confused: it either can't find it or doesn't know
which one you want (feast or famine).

HTH,

"Tom" wrote in message

oups.com...



Any ideas about why adding a conditional format would cause a running
sum control to display "#Name?" instead of the running sum value?
Without conditional formatting, it works fine.

Condition statement: [IS_PLACEHOLDER]

Note: IS_PLACEHOLDER is a Yes/No field in the underlying query.

Thanks!- Hide quoted text -

- Show quoted text -

Actually, what I have is txtQTY and txtCUM_QTY where the latter is the
running sum with the same data source as the former. The underlying
data source is [QTY_DUE] in the report's query.

Any other ideas?

Any other ideas?
Yep. You said that [IS_PLACEHOLDER] is a field in the underlying query,
fine. But is the field actually present anywhere on the report itself
(doesn't need to be visible, just present)? That makes a difference
sometimes. Not sure if it's non-presence would cause Conditional formatting
to generate a Name# error, but its easy enough to find out.

I did understand you to say that you don't get a #Name error if you don't
have Conditional Formatting applied, right? Its the addition of the
condition that causes the #Name error?

HTH,

"Tom" wrote in message
oups.com...
On Aug 2, 10:54 am, "George Nicholson"
wrote:
Make sure you don't have a control with the same name on the report.
#Name
indicates that Access is confused: it either can't find it or doesn't
know
which one you want (feast or famine).

HTH,

"Tom" wrote in message

oups.com...



Any ideas about why adding a conditional format would cause a running
sum control to display "#Name?" instead of the running sum value?
Without conditional formatting, it works fine.

Condition statement: [IS_PLACEHOLDER]

Note: IS_PLACEHOLDER is a Yes/No field in the underlying query.

Thanks!- Hide quoted text -

- Show quoted text -

Actually, what I have is txtQTY and txtCUM_QTY where the latter is the
running sum with the same data source as the former. The underlying
data source is [QTY_DUE] in the report's query.

Any other ideas?

On Aug 2, 12:51 pm, "George Nicholson"
wrote:
Any other ideas?

Yep. You said that [IS_PLACEHOLDER] is a field in the underlying query,
fine. But is the field actually present anywhere on the report itself
(doesn't need to be visible, just present)? That makes a difference
sometimes. Not sure if it's non-presence would cause Conditional formatting
to generate a Name# error, but its easy enough to find out.

I did understand you to say that you don't get a #Name error if you don't
have Conditional Formatting applied, right? Its the addition of the
condition that causes the #Name error?

HTH,

The field is not present on the form. I've always been adverse to
sticking invisible controls on forms and reports if I could avoid
doing so. I do have several other instances in this same application
of using conditional formatting tied to fields in the data source but
not present in a control on the report.

By way of background, the idea here is to display the quantity due for
each required delivery, then next to it display a running cumulative
total for the same data. The IS_PLACEHOLDER Yes/No field simply
highlights records for required deliveries that have not yet found
their way into the released contract, but are pending and Operations
needs to know they're coming.

If I'm not mistaken, the only difference in this case is a running sum
tied to the same field as a non-running sum.

I'm baffled (not that this is unusual...)

Thanks,

Tom