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 Stuart. -----Original Message----- 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 the criteria specified in a screen by the user, then executes the constructed selection statement. Something like (although the real one is more complex): SEL.CMD = 'SELECT CUSTOMER WITH CUST.NUM = "' : CUST.NUM : '" AND WITH CUST.TYPE = "' : CUST.TYPE : '"' EXECUTE SEL.CMD CAPTURING OUTPUT Indexes are built on the dictionaries and are working properly. When we test the constructed select statement at TCL, the results are retuned under 2 seconds. When it executes inside the BASIC program, it takes approximately 24 seconds to return the same results. We tried adding a NO.INDEX to the statement, which adds 6 seconds to the select at TCL but just a couple of seconds within the BASIC program. Nothing else we have tried has had any effect. Has anyone encountered this type of behavior? Thanks, Steve Long _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users