|
Marvin,--
We keep asking for the actual code because one of two things is
happening...
1) The code does exactly as you think it does and you've discovered a
bug in the OS
2) The code doesn't do exactly what you think it does...
Option 1 is possible, but option 2 is much, much more likely...
Charles
On Wed, Dec 11, 2019 at 8:56 AM Marvin Radding <
marvin.radding@xxxxxxxxxxxxxxxxxxxxx> wrote:
Scott,
I have provided the actual sql statement that is constructed. I don't
see how the code that does the construction will enlighten you any
further. It constructs the sql statement and in RPGLE it fails but in
STRSQL it finds the records. Why?
Thanks,
Marvin
No trees were killed in the sending of this message, but a large
number of electrons were terribly inconvenienced, traumatized,
triggered, and crying for their safe spaces.
-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf
Of Scott Mildenberger
Sent: Wednesday, December 11, 2019 7:48 AM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: A problem in embedded SQL
Can you show us the actual code where you are building and executing
the statement. I suspect something isn't happening the way it appear
to you and if we can see the actual code maybe someone can spot the issue.
Scott Mildenberger | Software Developer | Washington Corporations |
101 International Drive | Missoula, MT 59808 | Office: (406) 523-1536
| www.washcorp.com
-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Marvin Radding
Sent: Wednesday, December 11, 2019 8:26 AM
To: 'RPG programming on IBM i' <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: A problem in embedded SQL
Alan,
I construct the sql statement, perform a prepare, and then open the
cursor. When I do the fetch it fails to find the record. I copy the
sql statement from the RPGLE program and paste it into STRSQL and it
finds the record. I don't understand why there is a difference between the two.
Thanks,
Marvin
No trees were killed in the sending of this message, but a large
number of electrons were terribly inconvenienced, traumatized,
triggered, and crying for their safe spaces.
--
This is the RPG programming on IBM i (RPG400-L) mailing list To post
a message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our
affiliate
link: https://amazon.midrange.com
Notice: This e-mail transmission may contain information that is
proprietary, privileged and/or confidential and is intended
exclusively for the person(s) to whom it is addressed. This message
may also contain Protected Health Information (PHI) and must be
treated confidentially and handled in accordance with HIPAA and other federal and state privacy laws.
Any use, copying, retention or disclosure by any person other than
the intended recipient or the intended recipient's designees is
strictly prohibited. If you are not the intended recipient or their
designee, please notify the sender immediately and delete this e-mail
(and any accompanying attachments).
--
This is the RPG programming on IBM i (RPG400-L) mailing list To post
a message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our
affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
