From memory, it is the combination of calculated controls and conditional
formatting that is deadly, as they seem to trigger each other.
AFAIK, there is no real fix for the problem. You could try basing the form
on a query and putting the calculation into the query (as a calculated
field) instead of the ControlSource of the text box, to see if moving it
back a level takes you out of the loop.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Randy Harris" <ra***@SpamFree.com> wrote in message
news:xN******************@newssvr31.news.prodigy.c om...
Allen, I think you nailed it with the conditional formatting. But, I
can't figure out what to do to stop it. The formatting is pretty simple, if a
certain field (not the control source for the misbehaving control)
contains "(cont)" then change the background color of the control.
Is there some means of working around this, or must I simply shut off the
conditional formatting? I hate to remove a feature that the users have
gotten accustomed to.
The app is developed in A2K and there appears to be no problem until it is
run in A2K3.
"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:40***********************@freenews.iinet.net. au... Could be a problem with conditional formatting:
http://allenbrowne.com/bug-05.html
A2003 also has this display problem on WinXP:
http://allenbrowne.com/ser-46.html
"Randy Harris" <ra***@SpamFree.com> wrote in message
news:fb************@newssvr33.news.prodigy.com...
Strange problem on A2K. A continuous form is getting some sort of strobe effect on several systems that have been upgraded to Windows XP (never saw the problem on Win2K). One of the text boxes is flashing the
contents. Users are calling it "Slot Machine Mode". Anyone ever run into something like this?
