(normally).
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Gordon Glorfield
Sent: Monday, March 15, 2004 3:30 PM
To: 'U2 Users Discussion List'
Subject: RE: Strange results from I Descriptor
Yes, I'm doing that. Here is the code for the subr
(normally).
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Gordon Glorfield
Sent: Monday, March 15, 2004 3:30 PM
To: 'U2 Users Discussion List'
Subject: RE: Strange results from I Descriptor
Yes, I'm doing that. Here is the code for
Discussion List
Subject: RE: Strange results from I Descriptor
Don't do a select (or any query statement) within an I-descriptor subroutine
that gets called from query. That's what the message means.
Even if it did work it would be a dog.
If I need to do something like this in UniData
Don't do a select (or any query statement) within an I-descriptor subroutine that gets
called from query. That's what the message means.
Even if it did work it would be a dog.
If I need to do something like this in UniData I use the UniBasic index commands like
SETINDEX READFWD, etc and crea
EXIT
END
END
END
END
NEXT IDX
*
RETURN
Gordon J. Glorfield
Sr. Applications Developer
MAMSI (A UnitedHealth Company)
301-360-8839
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Not sure what you are doing but since it's in an i-descriptor and being used
as part of another listing, I'd use numbered selects in my subroutine to
make sure it doesn't bump heads with the current listing that's using the
i-descriptor.
HTH
Mike R.
-Original Message-
From: [EMAIL PROTE
