Scott,
Your example is a neat idea and works well with the example I gave. In my live site, I am downloading 1000+ records, and my replace dictionary is a parts table with 2,000 parts (changing ID for Part Name). So the replace SQL would have 2,000 nested replace statements. I'm not sure if that work, but I'll give it a try. Maybe I can do a match, loop through the matches to build the replace, but then the replace statement will be different for each record.
Thank you,
Jason