In message
<[email protected]>, Kevin
King <[email protected]> writes
I have a customer who has a view that appears like this in SQL:
SELECT ID,TYPE,BEGIN_DATE,END_DATE,FISCAL_PERIOD,PERIOD_OPEN FROM
T_CRP_FISCAL_PERIODS UNNEST NL_ALL
BEGIN_DATE,END_DATE,FISCAL_PERIOD,PERIOD_OPEN WHERE ID =
"001FISCAL.PERIODS";
This view, as far as I have been informed, was created via the VSG. And
this is valid SQL when run from the sql command line in Unidata. However,
when this view is used over ODBC, it returns "001FISCAL.PERIODS is not a
valid field name".
For this particular situation, changing the double quotes to single quotes
seems to do the trick, but that leads me to two questions for this esteemed
group:
a) Is VSG creating incompatible SQL, or does this appear to have been
created by a human?
b) Will we encounter other difficulties by this change from double quotes to
single quotes in the WHERE clause?
This sounds similar to a problem I had. Different, in that it was table
names, and I can't remember the details, but - I think it was the
MS-Access query generator - would select from a file but would assume
that file001 existed!
And it worked fine provided stuff was all MS (like reading/writing to
excel), but broke when it was trying to read from UV.
Not much help, but this might be another clue...
Cheers,
Wol
--
Anthony W. Youngman <[email protected]>
'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the
thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The man
lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998
Visit the MaVerick web-site - <http://www.maverick-dbms.org> Open Source Pick
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
