to do better data validation and that's another task I'm going to suggest
they need to do, but this is about queries not input.
I have 3 queries on SQLServer tables, and one on a Excel spreadsheet, each
containing a field called "Postcode" which is a varchar field in the
SQLServer, and has mostly numbers and some letters in the spreadsheet.
I am combining the four queries by looping over them and writing the output
to a query built by CFMX. Then I'm doing a query of a query to
de-duplicate the records, and sort them. That's where the application
gives an error when it encounters a postcode field with non-numeric content.
I can't see why that should matter. I'm not doing math on the field, I'm not
sorting on it. It's just a field, like name, suburb, country, email address
.. all the others. I cant see why it matters whether the contents of the
Postcode field are numbers or letters or dancing pigeons.
At the point where it throws the error, it's not trying to insert into a
database, or perform arithmetic, just SELECT in the Query of a Query. But
if there's a postcode field containing "NA" the whole thing hiccups.
WTF??
Cheers
Mike Kear
Windsor, NSW, Australia
AFP Webworks
http://afpwebworks.com
_____
From: Peter Tilbrook [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 8 June 2004 12:14 AM
To: CF-Talk
Subject: RE: QofQ problem -closing in on the problem..
Mike, if using CF use the <CFINPUT and use validate"numeric" or at least
"integer".
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
