IIRC, it should actually error and force you either to pick one or give them unique names (a.userid as bob, b.userid as fred).
Expecting Access to behave properly is like expecting teens not to drink. Sometimes it works, but most of the time, it's a mistake. --Ben Doom Jim McAtee wrote: > SELECT a.*, b.* > FROM user a INNER JOIN userprefs b ON b.userid = a.userid > WHERE username = 'bsmith' > > In the query there's a common column named 'userid'. Should the query > retun > > 1) one column named userid > 2) two columns named userid > 3) two columns with some type of unique name for each > > I find that the CF8 'Microsoft Access with Unicode' driver does #3, which > I hadn't seen before in other ODBC drivers. It returns two columns named > 'a.userid' and 'b.userid'. > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Enterprise web applications, build robust, secure scalable apps today - Try it now ColdFusion Today ColdFusion 8 beta - Build next generation apps Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:292008 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
