Hi Victor,
I would use the Data Link in this case... DP formulas seem to keep
triggering until they are stable, and the change in the first letter in the
result of you your CASE statement will ripple through and the formula
retriggered...
Using a Data Link on a U1 field, with a Axx::C calculated field through the
link, to display the lookup is the easiest to go... You do not have top up
arrow on the DataLink to get the value... just by entering the associated
letter in the U1 field will bring it through... It means that you still
display the letter (as that is really the underlying data)... An advantage
of this over using an additional real field, is that you are carrying extra
baggage with each record to enable a very simple user interface issue. The
calculated field adds no weight to the record, and to the application only
adds the weight of the lookup panel...
Regards
Brian
----- Original Message -----
From: "Ralph Alvy" <[EMAIL PROTECTED]>
To: "DataPerfect Users Discussion Group" <[email protected]>
Sent: Thursday, August 17, 2006 4:18 AM
Subject: Re: [Dataperf] Problem with CASE statement
Yeah, that's what I figured (needed 2 fields like the other problem), but
he
said that the field didn't blank when entering text (which was happening
with
the other problem). Given that, I thought he could try just switching the
order. If that fails, then 2 fields are needed, I guess.
Another possibility around all this is to refrain from using formulas at
all,
and just use a Data Link to a panel that holds all the possible values for
this field. This would make it easier to add other possible values later.
On Wed August 16 2006 09:15, Tim Rude wrote:
I think the same problem exists here. When the user enters "I" it gets
changed to "Statutory Instrument" which then triggers the formula to
update
the field again, and since the first letter is now "S" it changes again
to
"Statute".
Will switching the order of the statements change this?
I think two fields will be needed here also. Or you could change to
something like this:
P3F3 CASES
CASE CV ="S" OF "S - Statute" ENDOF
CASE CV ="I" OF "I - Statutory Instrument" ENDOF
DEFAULT ""
ENDCASES
Assuming that it doesn't cause a problem to have the indicator letter
within the field.
Tim Rude
----- Original Message -----
From: "Ralph Alvy" <[EMAIL PROTECTED]>
To: "DataPerfect Users Discussion Group" <[email protected]>
Sent: Wednesday, August 16, 2006 11:00 AM
Subject: Re: [Dataperf] Problem with CASE statement
> On Wednesday 16 August 2006 07:03, Victor Warner wrote:
> > also in the following CASE statement:
> >
> > P3F3 CASES
> > CASE CV ="S" OF "Statute" ENDOF
> > CASE CV ="I" OF "Statutory Instrument" ENDOF
> > DEFAULT ""
> > ENDCASES
> >
> > entering "I" produces the text for "S".
> >
> > Help with this would be very gratefully received.
>
> Try switching the order of the statements to this:
>
> P3F3 CASES
> CASE CV ="I" OF "Statutory Instrument" ENDOF
> CASE CV ="S" OF "Statute" ENDOF
> DEFAULT ""
> ENDCASES
> _______________________________________________
> Dataperf mailing list
> [email protected]
> http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
