Using FM Pro 6.0 on WindowsXP

When the data in two fields (A and B) on the same record do not match I want
to display a border around the changed field (B).
Field B will be the field that is always changed. Field A will always be
for viewing only.

I am currently using a case statement in a calcuation field to detect when A
and B are the same.
0 = Same
1= Different

Any ideas on how to accomplish this?




Thanks
Bigfoot1956

In article <KXUJe.947$Kp.191 (AT) bignews6 (DOT) bellsouth.net>, "bigfoot"
<REMOVEemailwwjCAPS (AT) bellsouth (DOT) netWORK> wrote:

Go to the layout and change to Layout Mode. Draw a rectangle around the
field using the normal Rectangle tool and change the line and fill
colours / styles to whatever you want. Then copy it.

Create a new Global field (g_FieldBorder) which is a Container. Put
this on the layout temporarily, then go into Browse Mode and paste in
the border graphic.

Create a new Calculation field:

FieldBorder Calculation, Container Result, Unstored
= If (FieldA = FieldB, "", g_FieldBorder)

This field will calculate as "" (empty) when the fields are the same,
but display the broder graphic when they're different.

Put this field on the layout and position it so that it is behind
FieldB and stretch it to an apropriate size. Also change the Grpahic
Format of the field to "Crop".

All done!

It might take a little playing to get it looking right. The easiest way
would be to change one of the fields so that they're different, then in
Layout Mode you can use the Show Sample Data and you'll be able to see
the grpahic as you stretch and position the field.




Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)

In article <090820051827060778%helpful_harry (AT) nom (DOT) de.plume.com>,
helpful_harry (AT) nom (DOT) de.plume.com says...
One note: there is often a "flicker" side effect to layering fields like
this, particularly noticable with graphics containers in client server
environments, when doing screen redraws (which occur when
advancing/retreating records and at many other times.) at least in my
experience.

Its not a big deal, but it can be distracting enough to be a problem
depending on the exact usage patterns of the layouts setup this way.

Thanks

Works Great.

Just Like PGA Golf. These Guys (and Gals) are GOOD.




"42" <nospam (AT) nospam (DOT) com> wrote

True.

A workaround in this particular case could be to use four fields: one
each for the top border, bottom border, and each side border. That way
the fields don't overlap, but are just placed next to each other.



Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)