edits help

Jay Ashworth jra at baylink.com
Fri May 27 12:41:09 PDT 2011


----- Original Message -----
> From: "Kenneth Brody" <kenbrody at spamcop.net>

> Without it, the "accept any amount of any character" part of the edit will
> accept all of the trailing spaces. Because the "&39;" expansion has
> increased the number characters in the field, the result no longer fits. By
> adding the "@" (which must come before the "*"), all of the trailing spaces
> are consumed, and are not part of the resulting value. Therefore, unless
> the expanded value is too long to fit, the edit "works". (Consider the
> case of a field consisting of nothing but apostrophes.) However, using
> DOEDIT() and passing an explicit length, can work around this.

But you're still not going to get any indication that you may have tried to
expand off the end of the destination field, as you could with a 'function',
right?

Cheers,
-- jra
-- 
Jay R. Ashworth                  Baylink                       jra at baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com         2000 Land Rover DII
St Petersburg FL USA      http://photo.imageinc.us             +1 727 647 1274


More information about the Filepro-list mailing list