You can try this yourself by adding an 'H' to field 4 of the VOC item
for QSELECT is suspect.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jonathan D
Smith
Sent: Thursday, 3 August 2006 8:01 p.m.
To: u2-users@listserver.u2ug.org
Subject: Fw: [U2] [UV] Q
I guess that's a question for IBM
Regards,
Mark Cornelissen
http://www.innovate-it.com
On Jul 31, 2006, at 16:10, Brian Whitehorn wrote:
Whats slightly confusing / inconsistent is that an EXECUTE with SELECT
/
SSELECT is catered for inside a transaction but not QSELECT? Why allow
/
cater fo
Assuming we're talking about uniVerse (and not uniData):
PERFORM is a different command. EXECUTE creates it's own execution
environment, where PERFORM does not. This means that with PERFORM you
can do a series of SELECT statements in the following way:
PERFORM "SELECT ANIMAL WITH SPECIES = 'Lio
Preform is an older version and sometime you get different results?
D Raven
[EMAIL PROTECTED]
cell (949)2282224
e Fax (815)4259364
P.O. Box 17811, Irvine CA 92623-7811
-- "Ray Wurlod" <[EMAIL PROTECTED]> wrote:
Have you tried PERFORM rather than EXECUTE?
---
u2-users mailing list
u2-users@lis
Have you tried PERFORM rather than EXECUTE?
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
> is there a way to allow an EXECUTE "QSELECT... "
> inside a transaction in a basic program. The HELP
BASIC EXECUTE specifies a few verbs that are allowed
inside transaction :
Have you tried: SELECT FILE SAVING FIELD.NAME ?
For example: SELECT CUSTOMERS SAVING KEY.ADR ?
It should be the equiv
