Hi, Birgitta:

Good point about care in the use of the "national characters" (@, # and $) especially in an "international" environment.

I simply answered James' question about what is allowed. I did not make any recommendations about usage.

Mark

> On 4/28/2011 1:17 PM, Birgitta Hauser wrote:
A-Z, 0-9, @, #, $ and _
I'd not use these special characters, because they are not international!!!
You can define a column/field with an @, while in my German environment a @
is not allowed. Instead I can define fields/columns with an §.
AFAIK in other environments $ is not allowed while the Pound (Currency) sign
can be used.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Mark S. Waterbury
Gesendet: Thursday, 28. April 2011 18:53
An: Midrange Systems Technical Discussion
Betreff: Re: Allowable characters in field names, was Re: Distributing UDFs

A-Z, 0-9, @, #, $ and _

> On 4/28/2011 12:47 PM, James Lampert wrote:
Alan Campin wrote:
You have to send the object and run the script to create the function.
And Rob wrote:
There are stored in QSYS2/SYSFUNCS.
Fascinating.

I was led to believe that field names (unless quoted) only accepted
uppercase letters, digits, and underscores. And yet I just learned
empirically that "#" is also allowed. Any other allowable characters I
don't know about?

--
JHHL

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2019 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].