> -----Original Message-----
> From: daniel kessler [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 22, 2005 11:24 AM
> To: CF-Talk
> Subject: RE: testing for undefined
>
> That's ok. This is just going to loop through the recordset and display
> the data so I use the same struct for each record, display it and then go
> on.
Now I'm really confused - why do this at all? Is there processing that's
not shown?
You can display everything as you want using just the query - why waste the
time to convert the query to something else to do this?
> I still have the original problem of testing for undefined.
Well - sort of. Queries aren't "sparse" arrays - their values should always
be "empty space" (although I think exceptions can arise when you build the
queries from scratch).
I think that
<cfif MyQuery.Col[Row] NEQ "">
< ... defined ... >
<cfelse>
< ... not defined ... >
</cfif>
Should do it.
However this really isn't "defined" but "empty" - CF treats nulls and empty
spaces the same in queries.
Jim Davis
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Logware (www.logware.us): a new and convenient web-based time tracking
application. Start tracking and documenting hours spent on a project or with a
client with Logware today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:210234
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
