yup.....makes sense....the subquery was returning multiple rows but not able

to join back 1-for-1. I think I was imputing some "smarts" into the Named Calculation

function that it didn't really have....

pretty much the same as what I had to begin with:

SELECT a.ContactID, a.[other fields],

COALESCE...

I finally got it to work.....I did use the Replace table with Named Query that you suggested, but I was able to use my original query. It still seems...

Hi Chuck,

My query actually worked fine in SSMS, however I reworked it per your example in the Edit Named Calculation window, but I get an error message:

"Only...

Hi Sarang,

Thanks for your reply.....it does look like I need to convert the datatypes

further upstream than where I was hoping to do it --- the app wouldn't...

Hi Chuck,

Thanks for your reply....

As you suggested, I ran the query in SSMS and came out with the same number

of records as in TableA which is the...

Thanks GSquared.....I'll try this out and see if it's what I'm looking for. Sounds promising!

Hi GSquared,

Thanks for your input....I think I understand the timestamp (system-generated number) concept,

but I'm not following how this would work in my case (and it may be...

Thanks for the replies......I've never used checksum before, but it sounds like it might be

the way to go --- I'll have to try it out.