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



Peter

It's good practice, IMO, to put spaces after commas
anyway. As I said, it helps my tired old eyes.

Glad you found it. I'd kind of wondered about language
differneces.

Cheers

Vern
> Hi gang,
>
> I found out why our SQL requires a blank after the commas when using the
> substr()  and other functions:
>
> If your decimal separator is *comma (as is the case on our systems), you
> need a blank after each comma, to indicate that you are entering the next
> parameter, and not a number with decimals.
>
> I just knew it had to be something simple (but well hidden).
>
> Note to IBM'ers monitoring this list:  Is it possible to have a new version
> of SQL where you can specify your own separator character, so that we could
> use for instance substr(field:1:1)?
>
> Regards,
>
> Peter Colpaert
> Application Developer
>
> Honda Europe NV
> Langerbruggestraat 104
> B-9000 GENT
> Peter.Colpaert@honda-eu.com
> Tel: +32 9 2501 334
> Fax: +32 9 2501 231
> ----------
> Yoda of Borg are we: Futile is resistance. Assimilate you, we will.
> ----------


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.