Have you checked the output of the select when performed from inside the
I-type? My guess is that it is generating a big ugly error, which is
why you are getting no records back. From my experience, performing
external selects from within an I-type is more than just a bad idea,
it's illegal.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ken Wallis
Sent: Thursday, 19 May 2005 16:42
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] UV PERFORM 'SELECT filename ...' in
I-Type {Unclassified}
HENDERSON MIKE, MR wrote:
Folks
Mike,
You've probably already figured it out or been told, but if you use a
numbered select list in your innermost executed select or selectindex
inside the i-desc subroutine, I'll bet you'll be ok.
I favour a standard that says select list 10 is a very temporary list
that a low level function
Folks,
We have had a puzzling situation where a particular subprogram works
differently when run from a test-harness from TCL, to when it is run as
an I-Type subroutine.
The sub-routine concerned is about three layers deep in the execution
sequence:-
Test-Harness does CALL A(parameters), A does
PROTECTED] On Behalf Of HENDERSON MIKE,
MR
Sent: Thursday, 19 May 2005 11:10 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] UV PERFORM 'SELECT filename ...' in I-Type
{Unclassified}
Folks,
We have had a puzzling situation where a particular subprogram works
differently when run from a test-harness
HENDERSON MIKE, MR wrote:
Folks,
We have had a puzzling situation where a particular subprogram works
differently when run from a test-harness from TCL, to when it
is run as an I-Type subroutine.
The sub-routine concerned is about three layers deep in the execution
sequence:-
