Hi All -
I am getting strange results with selections that I am hoping someone
else has encountered and can help me resolve.
We have SB+ running on UV. I don't have the same issues running on
Unidata.
I have a BASIC program I have written that constructs a select statement
based on
@listserver.u2ug.org
Subject: [U2] Strange Selection Behavior
Hi All -
I am getting strange results with selections that I am hoping someone
else has encountered and can help me resolve.
We have SB+ running on UV. I don't have the same issues running on
Unidata.
I have a BASIC program I have
-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Dave Davis
Sent: Tuesday, June 14, 2011 1:44 PM
To: U2 Users List
Subject: Re: [U2] Strange Selection Behavior
What do the queried fields look like?
Are they actual fields or calculated
Hi Steve,
Have you tried running the command as a LIST with an INFORM on the end? It
should show you how the system is treating the way the selection works. You may
need to data through an 'Enter' statement in the execute.
LIST CUSTOMER WITH CUST.NUM = 999 AND WITH CUST.TYPE = XXX INFORM
Hi Steve
This may be an issue of the EXECUTE creating another shell to perform the
select which the tcl prompt does not require. There has been past discussions
of the use of EXECUTE and PERFORM for this reason. However I am not sure that
there is an difference for Universe and the PERFORM
...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Steve Long
Sent: Wednesday, 15 June 2011 6:38 AM
To: U2-Users@listserver.u2ug.org
Subject: [U2] Strange Selection Behavior
Hi All -
I am getting strange results with selections that I am hoping someone
else has
If you have indexes built on these fields try using selectindex.
Jerry
On 6/14/2011 3:38 PM, Steve Long wrote:
Hi All -
I am getting strange results with selections that I am hoping someone
else has encountered and can help me resolve.
We have SB+ running on UV. I don't have the same
