iirc, you can't use the <> extraction syntax in unidata itypes. Instead of
@RECORD<15> you need to use something like EXTRACT(@RECORD,15). Or use an
attribute name like you did.
Cool error message though. It's a palindrome.
On Dec 5, 2013, at 4:44 PM, Doug Averch wrote:
> I was playing with EV
Quizzle Zik
It's a palindrome by the way
Sounds like you've hit such a strange error, that the systems programmer said
"I'll name this one later..."
-Original Message-
From: Allen Elwood RR
To: U2 Users List
Sent: Thu, Dec 5, 2013 1:52 pm
Subject: Re: [U2] Unidata error for the ages,
sounds like an error in the error message
error squared? lol...
On 12/5/2013 1:44 PM, Doug Averch wrote:
I was playing with EVAL trying to see why it would work in Universe
and not in Unidata. I typed in this sentence in Unidata 7.3.6:
list CRM.CUSTOMERS WITH EVAL "UPCASE(@RECORD<15>)" LIKE
I was playing with EVAL trying to see why it would work in Universe
and not in Unidata. I typed in this sentence in Unidata 7.3.6:
list CRM.CUSTOMERS WITH EVAL "UPCASE(@RECORD<15>)" LIKE "BILL..."
UPCASE(@RECORD<15>)
-^
Virtual Attribute Error: qz1zq syntax error
So what is qz1z
Not sure if this helps anyone...
There is an I DESC that we usually put in the DICT of most files.
Usually, when you go to use it, it hadn't been entered, while not difficult to
enter - just a pain.
I tried to put the IDESC in VOC, but I wasn't able to compile it
I was able to put it in the VOC