RE: [U2] [UV] controlling selects with unconverted data used for selection errors

2004-11-12 Thread Brian Leach
Troy,

IF you want more rigour in the selection, you can switch to an SQL
selection, e.g.

SELECT @ID TO SLIST 0 FROM MYFILE WHERE MYDATE = '31 FEB 04';

This will fail date recognition, swap to string recognition and then throw
out the statement because of the data type mismatch.

Brian. 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Buss, Troy (Logitek
Systems)
Sent: 11 November 2004 19:21
To: [EMAIL PROTECTED]
Subject: [U2] [UV] controlling selects with unconverted data used for
selection errors

Using universe 10.0.19...
 
When a user provides an invalid date value for a select, universe prints out
the error message bad data unconverted data used for selection
but goes on and does the select.
 
Is there a way to:
 
1. require that the retrieve command fail when this occurs by using a
keyword similiar to REQUIRE.INDEX as in REQUIRE.NO.ERRORS ?
 
or 
 
2. be able to get a result code from the command via the 'RETURNING ERRORS'
clause of an execute statement?
 
 
Personally, I think the command should outright fail when this occurs rather
than wasting the user's time and/or provding results that are not what was
intended.
 
Sample:
 
SELECT SOLI WITH DATE 2/31/04
Bad data 2/31/04 for conversion D2-.  Unconverted data used for
selection.
-- select proceeds for 2 minutes with zero items selected --
 
 
-Troy
---
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/


[U2] [UV] controlling selects with unconverted data used for selection errors

2004-11-11 Thread Buss, Troy \(Logitek Systems\)
Using universe 10.0.19...
 
When a user provides an invalid date value for a select, universe prints
out the error message bad data unconverted data used for selection
but goes on and does the select.
 
Is there a way to:
 
1. require that the retrieve command fail when this occurs by using a
keyword similiar to REQUIRE.INDEX as in REQUIRE.NO.ERRORS ?
 
or 
 
2. be able to get a result code from the command via the 'RETURNING
ERRORS' clause of an execute statement?
 
 
Personally, I think the command should outright fail when this occurs
rather than wasting the user's time and/or provding results that are not
what was intended.
 
Sample:
 
SELECT SOLI WITH DATE 2/31/04
Bad data 2/31/04 for conversion D2-.  Unconverted data used for
selection.
-- select proceeds for 2 minutes with zero items selected --
 
 
-Troy
---
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/