Hi Andy:

I found the following at the MSKB:

http://support.microsoft.com/default.aspx?scid=kb;en-us;197528

The above document lists two workarounds:

1) SET NOCOUNT ON

or

2) Use the .NextRecordset method

I haven't been able to make the .NextRecordset method...

Correction:

it succeeded with NOCOUNT set to ON.

Sorry for the confusion

JK

Hello Andy:

Thank you. That did the trick, but what trick did it do? Looking at the books online for SET NOCOUNT, I don't see anything that tells me why what...

Hi:

I think it's pretty straight-forward, but here it is. I'll never claim I don't make mistakes.

I get the same results with the simple test case published in the original...

That's a very nice approach. I really should have thought of that myself.

Thanks for the help.

JK

Well, I came up with the following solution. I used subqueries to return the SurnameIDs of all Surnames that included the requested Given Name, used AND IN to determine if...

quote:

---

I try to conform you syntax a little to make it run faster, but it should accomplish everything you want or lead...

Hi:

Thank you both for your responses. I'm a bit overwhelmed with things that I need to do right now, but I will look at both responses in detail as soon...

Hi:

Thank you Jim and Steve, for the responses.

No sooner than I sent that post than I came up with the following solution using (5) UPDATE queries:

-- Where no value now...

Well, that makes perfect sense! Thank you. I don't know why I missed the application of CASE here. There's a very different approach when using T-SQL than what I've been...