I assume there are trailing blanks in your original field that are not
trimmed off.
If you specify '%ith' exactly the last 3 characters in your original field
have to be ith.
You may try WHERE RTrim(YourColumn) like '%ith'
Or WHERE Right(RTrim(YourColumn), 3) = 'ith'
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: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im Auftrag von Booth
Martin
Gesendet: Monday, 16.11 2015 06:23
An: RPG programming on the IBM i / System i
Betreff: Embedded RPG and the WHERE LIKE
SQL has opened pleasing choices, choices which may bite me in the end.
In the meantime though I am liking the LIKE.
The instructions say one thing; I am getting another thing, which probably
means I didn't see some paragraph somewhere.
As I understand it this is a valid statement:
"Select: "%" is wildcard (Smi% gets Smith, as does %ith and %mit%.) Case
sensitive."
2 out of 3 work. Smi% works. %mit% works. %ith does not work. The field is
defined as varying. Does anyone recognize what has gone wrong?
(As an aside, is there a way to make this not case sensitive?)
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.
midrange.com
