In general it's possible to query such conditions in UI expressions. But it will depend on the particular scenario which way could be used and how suitable it would be in regard to the efforts and a possible performance impact.
I just played a bit with dummy data like:
load chr(recno() + 33) as Char, recno() as RecNo, 1 as Value autogenerate 120;
Pure theoretically it should be possible to use relational string operators like precedes and follows - but the "classical" set analysis syntax seems not to be applicable so that a if-loop syntax would be needed, like:
sum({< Char = {"=(Char follows 'A' and Char precedes 'Z') or Char = 'A' or Char = 'Z'"}>} Value)
whereby these operators doesn't be case sensitive and the char '@' which comes before 'A' creates rather strange results - which leads to the additionally or statement within the condition. If anyone has more experience with this feature please share your knowledge.
Another approach would be to create an appropriate search-string for the set analysis with something like:
sum({< Char = {"$(=concat(chr(valueloop(65,90,1)), '*","') & '*')"}>} Value)
which worked fine - but is also not case sensitive.
If the consideration of the case-sensitive is mandatory a classical if-loop will be needed, for example with:
if(match(left(Char, 1), '$(=concat(chr(valueloop(65,90,1)), ''',''') & '*')'), sum(Value))
If none of the mentioned approaches are practically enough you could of course flag these cases and/or by various of such requirements to categorize them within the script.
- Marcus
