@listserver.u2ug.org
Subject: Re: [U2] [UV] Suppress not found in RetrieVe
I think he means as in
SELECT VOC SAMPLE 100
LIST CUSTOMER
'A' not found
'F2' not found
And I don't know a way to suppress the messages, but I know a way to not GET
the messages :)
Try this
SELECT VOC SAMPLE 100
SELECT
Does anyone know of a RetrieVe option that will suppress the ' not found'
messages?
Thanks.
Perry
Perry Taylor
Senior MV Architect
ZirMed
888 West Market Street, Suite 400
Louisville, KY 40202
www.zirmed.comhttp://www.zirmed.com/
CONFIDENTIALITY NOTICE: This e-mail message, including
Do you mean on a SELECT or LIST? (Maybe I'm asking the obvious)
On Tue, Nov 15, 2011 at 1:43 PM, Perry Taylor perry.tay...@zirmed.comwrote:
Does anyone know of a RetrieVe option that will suppress the ' not
found' messages?
Thanks.
Perry
Perry Taylor
Senior MV Architect
ZirMed
that message
-Original Message-
From: John Thompson jthompson...@gmail.com
To: U2 Users List u2-users@listserver.u2ug.org
Sent: Tue, Nov 15, 2011 10:57 am
Subject: Re: [U2] [UV] Suppress not found in RetrieVe
Do you mean on a SELECT or LIST? (Maybe I'm asking the obvious)
On Tue, Nov
-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson
Sent: Tuesday, November 15, 2011 12:01 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] [UV] Suppress not found in RetrieVe
I think he means as in
SELECT VOC SAMPLE 100
LIST CUSTOMER
'A' not found
: [U2] [UV] Suppress not found in RetrieVe
I think he means as in
SELECT VOC SAMPLE 100
LIST CUSTOMER
'A' not found
'F2' not found
And I don't know a way to suppress the messages, but I know a way to not GET
the messages :)
Try this
SELECT VOC SAMPLE 100
SELECT CUSTOMER
do other selects
What I'm wondering as a higher-level question is: how important
are reports that are so volatile that they are invalid between
the select and the print? Certainly they're even more invalid
between printing and the time someone reads them. Another
approach might be to do a COPY or REFORMAT of
Hi Perry
You could use transaction control, where you prevent deletes until the report
is completed. For instance a GL report with Debits and Credits need to
balance, you cannot allow the database to change in the middle of the report,
so you wrap transaction control around to prevent updates