At 11:14 AM 3/4/2006, I myself wrote:
>I tried an alias, but in the end, it would be the same thing (i.e.,
>the alias would point back to the original master query) ...
Ok, it is working now. The solution was:
- use an alias for each column in the query of queries
- do not use the alias in the WHERE statement (reference the original
master query instead)
- do not use the alias in the ORDER BY statement (reference the
original master query instead)
- use the aliases within the CFOUTPUT tags (including the GROUP
parameter) to display the information
The query would then look something like this:
<cfquery dbtype="query" name="allRecords">
SELECT
listRegions.regionID AS AregionID,listRegions.region AS Aregion,
listCities.regionID AS BregionID,listCities.cityName AS BcityName,
listCities.customer AS Bcustomer
FROM listRegions, listCities
WHERE listRegions.regionID = listCities.regionID
ORDER BY listRegions.region ASC, listCities.cityName ASC
</cfquery>
<cfouput query="allRecords" group="Aregion">
#Aregion#
<cfoutput group="BcityName">
#BcityName#
<cfoutput>
#Bcustomer#
</cfoutput>
</cfouput>
</cfoutput>
This solution now works both on the developer server (MX 6) on my
desktop and on the production server (still have to get the specs for
that server to document the issue properly)
Regards,
Roberto
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:234194
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=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
