First, let me say that anything that can be done in the database should be. But, if you must do it this way, why don't you have the db return the extra columns as nulls then set the cell values. That way you don't have the extra query object being built.
Steve Sent from my iPhone On Mar 23, 2011, at 7:18 AM, "Kevin Parker" <[email protected]> wrote: > > I have a query where I need to add some extra stuff not in the database so > decide to create another query object with QueryNew. > > I loop over a query of the table to set cell values and add extra values to > each row etc. > > I output the record count for the original query and it shows 3 rows (which > is correct - there are three rows in the table) but when if do a cfdump of > the new query object its shows 6 rows, 3 with the original data and an extra > 3 with all cells showing [empty string] > > I have no idea where it's getting this from. > > Any clues please? TIA!!!!! > > > ++++++++++ > Kevin Parker > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:343221 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
