Thanks, that's very close to what I eventually used. There are actually no
duplicate records. The example was simplified and the other fields weren't
shown, but I have to match on fields that may contain duplicate values.
tom
<[EMAIL PROTECTED]> wrote in message
9B9D098EAC97D411938900805FFE1B62DA4901@GBVWFSMKS00003">news:9B9D098EAC97D411938900805FFE1B62DA4901@GBVWFSMKS00003...
> Is there any reason why you are keeping duplicate records in table 2. If
you
> kept it unique, then you wouldn't have this problem. But to do it with the
> data you have. You need to make a unique selection from table2 and then
link
> it back to table1. Something like this should work.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
