We're running our data mart on Progress 9.1E. Even with an extremely simple query like
"select g1.date DATE1 from glc g1"
the column-alias fails and I get the following: "** Unable to understand after -- "select". (247)".
"select g1.date alias DATE1 from glc g1" yields the same result.
"select g1.date as DATE1 from glc g1" results in "** Invalid datatype -- sample types are: char, integer, date, logical(222)".
Why am I unable to alias a column? I see other posts on the forum with snippets that appear to successfully alias columns. Is there a database parameter that allows/suppresses aliasing?
We don't have a Progress DBA here, but if there's a parameter that enables column-aliasing, please tell me what to change and I'll get our AIX administrator to change it if I don't have sufficient access.
Thanks for your help!
"select g1.date DATE1 from glc g1"
the column-alias fails and I get the following: "** Unable to understand after -- "select". (247)".
"select g1.date alias DATE1 from glc g1" yields the same result.
"select g1.date as DATE1 from glc g1" results in "** Invalid datatype -- sample types are: char, integer, date, logical(222)".
Why am I unable to alias a column? I see other posts on the forum with snippets that appear to successfully alias columns. Is there a database parameter that allows/suppresses aliasing?
We don't have a Progress DBA here, but if there's a parameter that enables column-aliasing, please tell me what to change and I'll get our AIX administrator to change it if I don't have sufficient access.
Thanks for your help!