× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




On 9-Jan-08, at 12:52 PM, rpg400-l-request@xxxxxxxxxxxx wrote:

> If I define a field as follow:

> D FOOT_NOTES_FIELD...
> D S 65535A INZ(*BLANKS)
>
> Doesn't that mean the field will hold 65535 characters?
>
> ...
>
> DOW NOT %EOF(RFQFOOTNPF);
>
> FOOT_NOTES_FIELD = %TRIM(FOOT_NOTES_FIELD) + %TRIM(FOTNOTE) + '|';
> READE (RFQ# : QSTRAT_ITEM_NUMBER) RFQFOOTNPF;
>
> ENDDO;

1) Given the current field definition, the second %TRIM is a waste of time and the spaces removed will immediately be reinserted when the resulting string is shorter than the max length.

2) It will be faster if you use %TRIMR rather that %TRIM as I doubt there will be any leading spaces.

3) You'd be better off using VARYING on the field definition then you can code:
FOOT_NOTES_FIELD += %TRIMR(FOTNOTE) + '|';
Then you never need to trim the field and (using %LEN) can always determine how big it is.



Jon Paris

www.Partner400.com
www.SystemiDeveloper.com



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.