asked on

Access Conditional formatting not working

Hi Experts,

I have the attached formatting conditions set to one of the controls of my continuous forms, and for some odd reason its not showing, when I do this for the control itself that's bound to the field used in condition it works, however I need it in another control that formats the original value (minutes) into hh:mm.
untitled.bmp

Jeffrey Coachman

I need it in another control that formats the original value (minutes) into hh:mm.

This works fine for me...

Can you post a sample db that exhibits this behavior?

ASKER CERTIFIED SOLUTION

Scott McDaniel (EE MVE )

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Dale Fye

Also, if your MinSchedThisWeek value uses the NZ( ) function inside a query, you may be expecting to see a numeric value, but when used in a query, the NZ() function will return a string, so you must explicitly convert that string to a number:

MinSchedThisWeek: cLng(NZ(X, 0))

bfuchs

ASKER

Hi Experts,

I finally boiled down this issue to be version related, as its only happening on office 2k (the version I am forced to use for programming, while there're still some users with that version..)

While that at least answers your questions, why is it working by you and proves the field is named correctly and its a number type etc...however these still does not help me, as I need it to work in 2000 as well...

Thanks,
Ben

SOLUTION

Jeffrey Coachman

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

bfuchs

ASKER

The solution was to have that formatting done in query instead of the form itself.
thanks for Scott for hinting me of that
and thanks for Jeff for pointing me back to Scott..

bfuchs

ASKER

BTW,

You know, its funny.

Its not funny at all, our manager does not want to approve upgrading to a new version unless I can prove that overall performance will increase significantly..
Unfortunately I only found it to be the opposite when compared to newer versions.
In addition to the fact that part of our app is an ADP that Microsoft abandoned in recent version..

Helen Feddema

The longer your manager waits to upgrade, the more painful it will be. I recently had the dubious pleasure of updating a number of databases for a client. Some of them were in Access 95 format. I had to make an Access 97 VM just so I could open them and resave them as Access 97 databases, then open those databases in an Access 2003 VM, save them in that format, and finally open the 2003 dbs in Access 2010, and upgrade them to that format. Not everything survived the multiple format transitions.

bfuchs

ASKER

@Helen_Feddema,
The reason our manager is hesitating of an upgrade is as follows.
We have an app that was orig written in 97, and eventually successful converted to 2000, since then we purchased a few licenses of 2003, and parts of our app are performing slower for those users (although each user has their own copy, and app was converted for them to 2003..).

Therefore you're right that when we are finally going to convert it will be harder, but he claims that its not worth to suffer in terms of performance until MSFT will finally come out with a product that addresses those issues...