table alias problem
Posted in 2005
Topics: Installation, Setup & Upgrades, Server Administration, Versions, Editions & End-of-Life
We have recently upgraded to IDS 9.40.FC6
on HPUX11i. We were on IDS 7.3xx on HPUX10.0.
WE are using Crystal Reports for a portion of our reporting needs.
We have run into a problem with a query from the Crystal report because of the
table alias:
fms441:tecsys.item item
We seem to only have this problem with this specific table. In dbaccess I can
replicate the problem for this same query, but it works for all other tables I
tried.
Has anyone seem this problem before?
Anthony said:
> We have recently upgraded to IDS 9.40.FC6 on HPUX11i. We were on IDS
> 7.3xx on HPUX10.0.
>
> WE are using Crystal Reports for a portion of our reporting needs.
>
> We have run into a problem with a query from the Crystal report because of
> the table alias:
> fms441:tecsys.item item
>
> We seem to only have this problem with this specific table. In dbaccess I
> can replicate the problem for this same query, but it works for all other
> tables I tried.
>
> Has anyone seem this problem before?
What problem?
--
Bye now,
Obnoxio
"C'est pas parce qu'on n'a rien à dire qu'il faut fermer sa gueule"
- Coluche
A smile is a gift that is free to the giver and precious to the recipient.
But giving someone the finger is free too, and I find it more personal and
sincere.
I think
"item" is a reserved word. I am not sure, which manual the
reserved words are documented.
Thank you,
Kannan Thirugnanam
-----Original Message-----
From: forum.subscriber@iiug.org [mailto:forum.subscriber@iiug.org] On
Behalf Of Anthony
Sent: Tuesday, June 14, 2005 1:55 PM
To: ids@iiug.org
Subject: table alias problem [5148]
We have recently upgraded to IDS 9.40.FC6 on HPUX11i. We were on IDS
7.3xx on HPUX10.0.
WE are using Crystal Reports for a portion of our reporting needs.
We have run into a problem with a query from the Crystal report because
of the table alias:
fms441:tecsys.item item
We seem to only have this problem with this specific table. In dbaccess
I can replicate the problem for this same query, but it works for all
other tables I tried.
Has anyone seem this problem before?
***** Jackson Hewitt Email Disclaimer *****
The sender believes that this E-mail and any attachments were free of any
virus, worm,
Trojan horse, and/or malicious code when sent. This message and its
attachments could
have been infected during transmission. By reading the message and opening any
attachments, the recipient accepts full responsibility for taking protective
and remedial
action about viruses and other defects. The sender's business entity is not
liable for any
loss or damage arising in any way from this message or its attachments.
Privileged/Confidential Information may be contained in this message. If you
are not the
addressee indicated in this message (or responsible for delivery of the
message to such
person), you may not copy or deliver this message to anyone. In such case, you
should
destroy this message and kindly notify the sender by reply email.
Anthony wrote
> We have recently upgraded to IDS 9.40.FC6 on HPUX11i. We
> were on IDS 7.3xx on HPUX10.0.
>
> WE are using Crystal Reports for a portion of our reporting needs.
>
> We have run into a problem with a query from the Crystal
> report because of the table alias:
> fms441:tecsys.item item
>
> We seem to only have this problem with this specific table.
> In dbaccess I can replicate the problem for this same query,
> but it works for all other tables I tried.
>
> Has anyone seem this problem before?
ITEM is a reserverd word in 9.4.
Colin Bull
=======================================================================
This email may contain confidential and privileged information and is intended
for the named or
authorised recipients only. If you are not the named or authorised recipient
of this email,
please note that any copying, distribution, disclosure or use of its contents
is strictly
prohibited. If you have received this email in error please notify the sender
immediately and
then destroy it. The views expressed in this email are not necessarily those
held by VNL, and VNL
does not accept any liability for any action taken in reliance on the contents
of this message.
VNL does not guarantee that the integrity of this email has been maintained,
nor that it is free
of viruses, interceptions or interference.
_______________________________________________________________________
This email has been scanned for all known viruses by the MessageLabs Email
Security System.
_______________________________________________________________________