Conditional Formatting on client

  • Thread starter Thread starter Chegu Tom
  • Start date Start date
C

Chegu Tom

I have a report that uses conditional formatting to shade controls
It runs without problem on access 2000, 2002, 2003 and 2007

Two 2003 clients have problems with the conditional formatting.
No matter what I put in for an expression it formats as if the criteria is
not met
even Expression TRUE or expression 1=1 won't format the controls

The expressions I have work fine for all the other clients (about 20 of
them)

What settings on that client could cause it to ignore conditional
formatting?
 
There is something wrong with the value in the field for that client you are
basing conditional formatting on. Perhaps it is a text value and for that
client there is a leading or trailing space that is not obvious.

Steve
(e-mail address removed)
 
Steve

No they are all numeric values and they are all taken from the same backend
as the other clients who all display correctly.

I even tried setting the criterian to expression and set the value to [true]
which should trigger the formatting but does not.
 
Tom

Although they are all numeric values, are they Text data type? If so, see if
you have a leading or trailing space.

I would also try opening the table and for the problematic client, delete
the value in the field and reenter it. Then try your conditional formatting.

If the above fails, post a couple of examples of the values that work and
post the value that does not work. Also post the criterion.

Steve



Chegu Tom said:
Steve

No they are all numeric values and they are all taken from the same
backend as the other clients who all display correctly.

I even tried setting the criterian to expression and set the value to
[true] which should trigger the formatting but does not.



Steve said:
There is something wrong with the value in the field for that client you
are basing conditional formatting on. Perhaps it is a text value and for
that client there is a leading or trailing space that is not obvious.

Steve
(e-mail address removed)
Click to expand...
Click to expand...
 
Steve

I know about spaces and text fields, they are all numeric values in numeric
fields. a typacle criterian is [CutN]=[CutD] (cuts needed = cuts done)
that control will be shaded. There are 20 such fields in this report and
hundreds of rows.

Please Note
If I take a front end DB with this report and put it on a shared drive (the
backend is also shared).
Open it on the shared drive with any other Access client (2000, 2002,
2003, 2007) and all of the criteria work, all of the formatting works
Open it on the shared drive with these two specific Access 2003 clients
and none of the criteria work.

This really has me puzzled. This report has been working for 5 years on
many different clients and still works on all others.

If we can't figure some client setting, I may have to reinstall the problem
clients.



Steve said:
Tom

Although they are all numeric values, are they Text data type? If so, see
if you have a leading or trailing space.

I would also try opening the table and for the problematic client, delete
the value in the field and reenter it. Then try your conditional
formatting.

If the above fails, post a couple of examples of the values that work and
post the value that does not work. Also post the criterion.

Steve



Chegu Tom said:
Steve

No they are all numeric values and they are all taken from the same
backend as the other clients who all display correctly.

I even tried setting the criterian to expression and set the value to
[true] which should trigger the formatting but does not.



Steve said:
There is something wrong with the value in the field for that client you
are basing conditional formatting on. Perhaps it is a text value and for
that client there is a leading or trailing space that is not obvious.

Steve
(e-mail address removed)


I have a report that uses conditional formatting to shade controls
It runs without problem on access 2000, 2002, 2003 and 2007

Two 2003 clients have problems with the conditional formatting.
No matter what I put in for an expression it formats as if the criteria
is not met
even Expression TRUE or expression 1=1 won't format the controls

The expressions I have work fine for all the other clients (about 20 of
them)

What settings on that client could cause it to ignore conditional
formatting?
Click to expand...
Click to expand...
Click to expand...
 
Chegu Tom,

Things to check on those two machines...

1. Check Tools - References (behind any form) and make sure the machines
where it is not working have the same References as the machines that are
working. If any say *MISSING* you'll want to fix those.

2. Make sure the installs match. Conditional Formatting is not always
installed with Access unless selecting Custom Install.

3. Make sure a Default printer has been assigned in Windows and make sure
Access can find it.

4. Check the SP? version of the machines that do work against the ones that
don't work and make sure everyone is on the same version.

5. Also check the Macro Settings on machines working against machines not
working.

Hopefully, one of the above will find the issue!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

Steve

I know about spaces and text fields, they are all numeric values in numeric
fields. a typacle criterian is [CutN]=[CutD] (cuts needed = cuts done)
that control will be shaded. There are 20 such fields in this report and
hundreds of rows.

Please Note
If I take a front end DB with this report and put it on a shared drive (the
backend is also shared).
Open it on the shared drive with any other Access client (2000, 2002,
2003, 2007) and all of the criteria work, all of the formatting works
Open it on the shared drive with these two specific Access 2003 clients
and none of the criteria work.

This really has me puzzled. This report has been working for 5 years on
many different clients and still works on all others.

If we can't figure some client setting, I may have to reinstall the problem
clients.



Steve said:
Tom

Although they are all numeric values, are they Text data type? If so, see
if you have a leading or trailing space.

I would also try opening the table and for the problematic client, delete
the value in the field and reenter it. Then try your conditional
formatting.

If the above fails, post a couple of examples of the values that work and
post the value that does not work. Also post the criterion.

Steve



Chegu Tom said:
Steve

No they are all numeric values and they are all taken from the same
backend as the other clients who all display correctly.

I even tried setting the criterian to expression and set the value to
[true] which should trigger the formatting but does not.



Steve said:
There is something wrong with the value in the field for that client you
are basing conditional formatting on. Perhaps it is a text value and for
that client there is a leading or trailing space that is not obvious.

Steve
(e-mail address removed)


I have a report that uses conditional formatting to shade controls
It runs without problem on access 2000, 2002, 2003 and 2007

Two 2003 clients have problems with the conditional formatting.
No matter what I put in for an expression it formats as if the criteria
is not met
even Expression TRUE or expression 1=1 won't format the controls

The expressions I have work fine for all the other clients (about 20 of
them)

What settings on that client could cause it to ignore conditional
formatting?
Click to expand...
Click to expand...
Click to expand...
 
Gina

Thanks for your list. It was the Office SP version. SP3 is the problem

The Machines that don't work are running Access 2003 SP3.
The ones that work are using Access 2003 SP2 (and 2000, 2002, 2007)

Is there an easy way to back out a service pack, or a patch to fix it?

I tend to assume that the newest patch or SP is the best and that sometimes
proves false.

Thanks again. This one was driving me nuts. I tried so many criteria and
formats

Tom


Gina Whipp said:
Chegu Tom,

Things to check on those two machines...

1. Check Tools - References (behind any form) and make sure the machines
where it is not working have the same References as the machines that are
working. If any say *MISSING* you'll want to fix those.

2. Make sure the installs match. Conditional Formatting is not always
installed with Access unless selecting Custom Install.

3. Make sure a Default printer has been assigned in Windows and make sure
Access can find it.

4. Check the SP? version of the machines that do work against the ones
that
don't work and make sure everyone is on the same version.

5. Also check the Macro Settings on machines working against machines not
working.

Hopefully, one of the above will find the issue!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

Steve

I know about spaces and text fields, they are all numeric values in
numeric
fields. a typacle criterian is [CutN]=[CutD] (cuts needed = cuts done)
that control will be shaded. There are 20 such fields in this report and
hundreds of rows.

Please Note
If I take a front end DB with this report and put it on a shared drive
(the
backend is also shared).
Open it on the shared drive with any other Access client (2000, 2002,
2003, 2007) and all of the criteria work, all of the formatting works
Open it on the shared drive with these two specific Access 2003 clients
and none of the criteria work.

This really has me puzzled. This report has been working for 5 years on
many different clients and still works on all others.

If we can't figure some client setting, I may have to reinstall the
problem
clients.



Steve said:
Tom

Although they are all numeric values, are they Text data type? If so, see
if you have a leading or trailing space.

I would also try opening the table and for the problematic client, delete
the value in the field and reenter it. Then try your conditional
formatting.

If the above fails, post a couple of examples of the values that work and
post the value that does not work. Also post the criterion.

Steve



Chegu Tom said:
Steve

No they are all numeric values and they are all taken from the same
backend as the other clients who all display correctly.

I even tried setting the criterian to expression and set the value to
[true] which should trigger the formatting but does not.



There is something wrong with the value in the field for that client
you
are basing conditional formatting on. Perhaps it is a text value and
for
that client there is a leading or trailing space that is not obvious.

Steve
(e-mail address removed)


I have a report that uses conditional formatting to shade controls
It runs without problem on access 2000, 2002, 2003 and 2007

Two 2003 clients have problems with the conditional formatting.
No matter what I put in for an expression it formats as if the
criteria
is not met
even Expression TRUE or expression 1=1 won't format the
controls

The expressions I have work fine for all the other clients (about 20
of
them)

What settings on that client could cause it to ignore conditional
formatting?
Click to expand...
Click to expand...
Click to expand...
 
It seems SP3 caused many problems. Microsoft has a hotfix that I will try
Kb945674. I haven't seen this one listed in the known problems but I hope
it contains the cure.


Chegu Tom said:
Gina

Thanks for your list. It was the Office SP version. SP3 is the problem

The Machines that don't work are running Access 2003 SP3.
The ones that work are using Access 2003 SP2 (and 2000, 2002, 2007)

Is there an easy way to back out a service pack, or a patch to fix it?

I tend to assume that the newest patch or SP is the best and that
sometimes proves false.

Thanks again. This one was driving me nuts. I tried so many criteria and
formats

Tom


Gina Whipp said:
Chegu Tom,

Things to check on those two machines...

1. Check Tools - References (behind any form) and make sure the machines
where it is not working have the same References as the machines that are
working. If any say *MISSING* you'll want to fix those.

2. Make sure the installs match. Conditional Formatting is not always
installed with Access unless selecting Custom Install.

3. Make sure a Default printer has been assigned in Windows and make
sure
Access can find it.

4. Check the SP? version of the machines that do work against the ones
that
don't work and make sure everyone is on the same version.

5. Also check the Macro Settings on machines working against machines
not
working.

Hopefully, one of the above will find the issue!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" -
Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

Steve

I know about spaces and text fields, they are all numeric values in
numeric
fields. a typacle criterian is [CutN]=[CutD] (cuts needed = cuts done)
that control will be shaded. There are 20 such fields in this report and
hundreds of rows.

Please Note
If I take a front end DB with this report and put it on a shared drive
(the
backend is also shared).
Open it on the shared drive with any other Access client (2000, 2002,
2003, 2007) and all of the criteria work, all of the formatting works
Open it on the shared drive with these two specific Access 2003
clients
and none of the criteria work.

This really has me puzzled. This report has been working for 5 years on
many different clients and still works on all others.

If we can't figure some client setting, I may have to reinstall the
problem
clients.



Steve said:
Tom

Although they are all numeric values, are they Text data type? If so,
see
if you have a leading or trailing space.

I would also try opening the table and for the problematic client,
delete
the value in the field and reenter it. Then try your conditional
formatting.

If the above fails, post a couple of examples of the values that work
and
post the value that does not work. Also post the criterion.

Steve



Steve

No they are all numeric values and they are all taken from the same
backend as the other clients who all display correctly.

I even tried setting the criterian to expression and set the value to
[true] which should trigger the formatting but does not.



There is something wrong with the value in the field for that client
you
are basing conditional formatting on. Perhaps it is a text value and
for
that client there is a leading or trailing space that is not obvious.

Steve
(e-mail address removed)


I have a report that uses conditional formatting to shade controls
It runs without problem on access 2000, 2002, 2003 and 2007

Two 2003 clients have problems with the conditional formatting.
No matter what I put in for an expression it formats as if the
criteria
is not met
even Expression TRUE or expression 1=1 won't format the
controls

The expressions I have work fine for all the other clients (about 20
of
them)

What settings on that client could cause it to ignore conditional
formatting?
Click to expand...
Click to expand...
Click to expand...
 
Chegu Tom,

To be honest, all my Clients on Access 2003 I have hidden that update from
them. It seems to break more then it fixes. The only way I know to fix it
is to uninstall Access and reinstall up to SP2. Though bear in mind SP2
will not be supported forever... well that probably goes for Office 2003 as
soon enough 2010 will will be out.

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

Gina

Thanks for your list. It was the Office SP version. SP3 is the problem

The Machines that don't work are running Access 2003 SP3.
The ones that work are using Access 2003 SP2 (and 2000, 2002, 2007)

Is there an easy way to back out a service pack, or a patch to fix it?

I tend to assume that the newest patch or SP is the best and that sometimes
proves false.

Thanks again. This one was driving me nuts. I tried so many criteria and
formats

Tom


Gina Whipp said:
Chegu Tom,

Things to check on those two machines...

1. Check Tools - References (behind any form) and make sure the machines
where it is not working have the same References as the machines that are
working. If any say *MISSING* you'll want to fix those.

2. Make sure the installs match. Conditional Formatting is not always
installed with Access unless selecting Custom Install.

3. Make sure a Default printer has been assigned in Windows and make sure
Access can find it.

4. Check the SP? version of the machines that do work against the ones
that
don't work and make sure everyone is on the same version.

5. Also check the Macro Settings on machines working against machines not
working.

Hopefully, one of the above will find the issue!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

Steve

I know about spaces and text fields, they are all numeric values in
numeric
fields. a typacle criterian is [CutN]=[CutD] (cuts needed = cuts done)
that control will be shaded. There are 20 such fields in this report and
hundreds of rows.

Please Note
If I take a front end DB with this report and put it on a shared drive
(the
backend is also shared).
Open it on the shared drive with any other Access client (2000, 2002,
2003, 2007) and all of the criteria work, all of the formatting works
Open it on the shared drive with these two specific Access 2003 clients
and none of the criteria work.

This really has me puzzled. This report has been working for 5 years on
many different clients and still works on all others.

If we can't figure some client setting, I may have to reinstall the
problem
clients.



Steve said:
Tom

Although they are all numeric values, are they Text data type? If so, see
if you have a leading or trailing space.

I would also try opening the table and for the problematic client, delete
the value in the field and reenter it. Then try your conditional
formatting.

If the above fails, post a couple of examples of the values that work and
post the value that does not work. Also post the criterion.

Steve



Chegu Tom said:
Steve

No they are all numeric values and they are all taken from the same
backend as the other clients who all display correctly.

I even tried setting the criterian to expression and set the value to
[true] which should trigger the formatting but does not.



There is something wrong with the value in the field for that client
you
are basing conditional formatting on. Perhaps it is a text value and
for
that client there is a leading or trailing space that is not obvious.

Steve
(e-mail address removed)


I have a report that uses conditional formatting to shade controls
It runs without problem on access 2000, 2002, 2003 and 2007

Two 2003 clients have problems with the conditional formatting.
No matter what I put in for an expression it formats as if the
criteria
is not met
even Expression TRUE or expression 1=1 won't format the
controls

The expressions I have work fine for all the other clients (about 20
of
them)

What settings on that client could cause it to ignore conditional
formatting?
Click to expand...
Click to expand...
Click to expand...
 
Let us know... there are probably many folks that would like to know!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

It seems SP3 caused many problems. Microsoft has a hotfix that I will try
Kb945674. I haven't seen this one listed in the known problems but I hope
it contains the cure.


Chegu Tom said:
Gina

Thanks for your list. It was the Office SP version. SP3 is the problem

The Machines that don't work are running Access 2003 SP3.
The ones that work are using Access 2003 SP2 (and 2000, 2002, 2007)

Is there an easy way to back out a service pack, or a patch to fix it?

I tend to assume that the newest patch or SP is the best and that
sometimes proves false.

Thanks again. This one was driving me nuts. I tried so many criteria and
formats

Tom


Gina Whipp said:
Chegu Tom,

Things to check on those two machines...

1. Check Tools - References (behind any form) and make sure the machines
where it is not working have the same References as the machines that are
working. If any say *MISSING* you'll want to fix those.

2. Make sure the installs match. Conditional Formatting is not always
installed with Access unless selecting Custom Install.

3. Make sure a Default printer has been assigned in Windows and make
sure
Access can find it.

4. Check the SP? version of the machines that do work against the ones
that
don't work and make sure everyone is on the same version.

5. Also check the Macro Settings on machines working against machines
not
working.

Hopefully, one of the above will find the issue!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" -
Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

Steve

I know about spaces and text fields, they are all numeric values in
numeric
fields. a typacle criterian is [CutN]=[CutD] (cuts needed = cuts done)
that control will be shaded. There are 20 such fields in this report and
hundreds of rows.

Please Note
If I take a front end DB with this report and put it on a shared drive
(the
backend is also shared).
Open it on the shared drive with any other Access client (2000, 2002,
2003, 2007) and all of the criteria work, all of the formatting works
Open it on the shared drive with these two specific Access 2003
clients
and none of the criteria work.

This really has me puzzled. This report has been working for 5 years on
many different clients and still works on all others.

If we can't figure some client setting, I may have to reinstall the
problem
clients.



Steve said:
Tom

Although they are all numeric values, are they Text data type? If so,
see
if you have a leading or trailing space.

I would also try opening the table and for the problematic client,
delete
the value in the field and reenter it. Then try your conditional
formatting.

If the above fails, post a couple of examples of the values that work
and
post the value that does not work. Also post the criterion.

Steve



Steve

No they are all numeric values and they are all taken from the same
backend as the other clients who all display correctly.

I even tried setting the criterian to expression and set the value to
[true] which should trigger the formatting but does not.



There is something wrong with the value in the field for that client
you
are basing conditional formatting on. Perhaps it is a text value and
for
that client there is a leading or trailing space that is not obvious.

Steve
(e-mail address removed)


I have a report that uses conditional formatting to shade controls
It runs without problem on access 2000, 2002, 2003 and 2007

Two 2003 clients have problems with the conditional formatting.
No matter what I put in for an expression it formats as if the
criteria
is not met
even Expression TRUE or expression 1=1 won't format the
controls

The expressions I have work fine for all the other clients (about 20
of
them)

What settings on that client could cause it to ignore conditional
formatting?
Click to expand...
Click to expand...
Click to expand...
 
The Hot fix didn't work for this problem

How do I HIDE that SP from all of my 2003 clients?


Gina Whipp said:
Let us know... there are probably many folks that would like to know!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

It seems SP3 caused many problems. Microsoft has a hotfix that I will try
Kb945674. I haven't seen this one listed in the known problems but I hope
it contains the cure.


Chegu Tom said:
Gina

Thanks for your list. It was the Office SP version. SP3 is the problem

The Machines that don't work are running Access 2003 SP3.
The ones that work are using Access 2003 SP2 (and 2000, 2002, 2007)

Is there an easy way to back out a service pack, or a patch to fix it?

I tend to assume that the newest patch or SP is the best and that
sometimes proves false.

Thanks again. This one was driving me nuts. I tried so many criteria
and
formats

Tom


Gina Whipp said:
Chegu Tom,

Things to check on those two machines...

1. Check Tools - References (behind any form) and make sure the
machines
where it is not working have the same References as the machines that
are
working. If any say *MISSING* you'll want to fix those.

2. Make sure the installs match. Conditional Formatting is not always
installed with Access unless selecting Custom Install.

3. Make sure a Default printer has been assigned in Windows and make
sure
Access can find it.

4. Check the SP? version of the machines that do work against the ones
that
don't work and make sure everyone is on the same version.

5. Also check the Macro Settings on machines working against machines
not
working.

Hopefully, one of the above will find the issue!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" -
Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

Steve

I know about spaces and text fields, they are all numeric values in
numeric
fields. a typacle criterian is [CutN]=[CutD] (cuts needed = cuts
done)
that control will be shaded. There are 20 such fields in this report
and
hundreds of rows.

Please Note
If I take a front end DB with this report and put it on a shared drive
(the
backend is also shared).
Open it on the shared drive with any other Access client (2000, 2002,
2003, 2007) and all of the criteria work, all of the formatting works
Open it on the shared drive with these two specific Access 2003
clients
and none of the criteria work.

This really has me puzzled. This report has been working for 5 years on
many different clients and still works on all others.

If we can't figure some client setting, I may have to reinstall the
problem
clients.



Tom

Although they are all numeric values, are they Text data type? If so,
see
if you have a leading or trailing space.

I would also try opening the table and for the problematic client,
delete
the value in the field and reenter it. Then try your conditional
formatting.

If the above fails, post a couple of examples of the values that work
and
post the value that does not work. Also post the criterion.

Steve



Steve

No they are all numeric values and they are all taken from the same
backend as the other clients who all display correctly.

I even tried setting the criterian to expression and set the value to
[true] which should trigger the formatting but does not.



There is something wrong with the value in the field for that client
you
are basing conditional formatting on. Perhaps it is a text value and
for
that client there is a leading or trailing space that is not obvious.

Steve
(e-mail address removed)


I have a report that uses conditional formatting to shade controls
It runs without problem on access 2000, 2002, 2003 and 2007

Two 2003 clients have problems with the conditional formatting.
No matter what I put in for an expression it formats as if the
criteria
is not met
even Expression TRUE or expression 1=1 won't format the
controls

The expressions I have work fine for all the other clients (about 20
of
them)

What settings on that client could cause it to ignore conditional
formatting?
Click to expand...
Click to expand...
Click to expand...
 
Chegu Tom,

Unfortunately, I do not know how to it via code, not even sure it can be
done that way, it has to be done per machine. When you go the Update site,
once you click on the update there is option to hide the update. I hesitate
to give exact instructions as they vary depending on Windows version. It
will also vary if the company *rolls out* update because then it can be done
in the background and the Users will never know because they will never get
offered that option.

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

The Hot fix didn't work for this problem

How do I HIDE that SP from all of my 2003 clients?


Gina Whipp said:
Let us know... there are probably many folks that would like to know!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

It seems SP3 caused many problems. Microsoft has a hotfix that I will try
Kb945674. I haven't seen this one listed in the known problems but I hope
it contains the cure.


Chegu Tom said:
Gina

Thanks for your list. It was the Office SP version. SP3 is the problem

The Machines that don't work are running Access 2003 SP3.
The ones that work are using Access 2003 SP2 (and 2000, 2002, 2007)

Is there an easy way to back out a service pack, or a patch to fix it?

I tend to assume that the newest patch or SP is the best and that
sometimes proves false.

Thanks again. This one was driving me nuts. I tried so many criteria
and
formats

Tom


Gina Whipp said:
Chegu Tom,

Things to check on those two machines...

1. Check Tools - References (behind any form) and make sure the
machines
where it is not working have the same References as the machines that
are
working. If any say *MISSING* you'll want to fix those.

2. Make sure the installs match. Conditional Formatting is not always
installed with Access unless selecting Custom Install.

3. Make sure a Default printer has been assigned in Windows and make
sure
Access can find it.

4. Check the SP? version of the machines that do work against the ones
that
don't work and make sure everyone is on the same version.

5. Also check the Macro Settings on machines working against machines
not
working.

Hopefully, one of the above will find the issue!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" -
Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

Steve

I know about spaces and text fields, they are all numeric values in
numeric
fields. a typacle criterian is [CutN]=[CutD] (cuts needed = cuts
done)
that control will be shaded. There are 20 such fields in this report
and
hundreds of rows.

Please Note
If I take a front end DB with this report and put it on a shared drive
(the
backend is also shared).
Open it on the shared drive with any other Access client (2000, 2002,
2003, 2007) and all of the criteria work, all of the formatting works
Open it on the shared drive with these two specific Access 2003
clients
and none of the criteria work.

This really has me puzzled. This report has been working for 5 years on
many different clients and still works on all others.

If we can't figure some client setting, I may have to reinstall the
problem
clients.



Tom

Although they are all numeric values, are they Text data type? If so,
see
if you have a leading or trailing space.

I would also try opening the table and for the problematic client,
delete
the value in the field and reenter it. Then try your conditional
formatting.

If the above fails, post a couple of examples of the values that work
and
post the value that does not work. Also post the criterion.

Steve



Steve

No they are all numeric values and they are all taken from the same
backend as the other clients who all display correctly.

I even tried setting the criterian to expression and set the value to
[true] which should trigger the formatting but does not.



There is something wrong with the value in the field for that client
you
are basing conditional formatting on. Perhaps it is a text value and
for
that client there is a leading or trailing space that is not obvious.

Steve
(e-mail address removed)


I have a report that uses conditional formatting to shade controls
It runs without problem on access 2000, 2002, 2003 and 2007

Two 2003 clients have problems with the conditional formatting.
No matter what I put in for an expression it formats as if the
criteria
is not met
even Expression TRUE or expression 1=1 won't format the
controls

The expressions I have work fine for all the other clients (about 20
of
them)

What settings on that client could cause it to ignore conditional
formatting?
Click to expand...
Click to expand...
Click to expand...
 
Back
Top