× 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.



Hi, Peter

This is strange to me. I've _never_ had to put spaces after commas. Either
version of the substr you describe has worked. AFAIK, SQL doesn't care
about spaces - you put in as many as you want, or none at all, and it's OK.
I'm going to try a few things again, to verify this.

Could there be any differences with system language - US as against
Deutschland, etc.?

OTOH, who can argue with success?

Regards

Vern

At 02:44 PM 8/28/02 +0200, you wrote:

>Jaime,
>
>I would not know, but I noticed that SQL on the iSeries requires a blank
>after each comma in the statements, for instance substr(field,1,1) will not
>work, whereas substr(field, 1, 1) is OK.
>
>Regards,
>
>Peter Colpaert



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.