This should do the trick... the SELECT is where the rubber meets the road... the rest of the stuff is just setting up for the demo of the SELECT...

--===== If...

Actually, I've resurrected some old code I was working on to make a WebTask that would make some pretty output... the output does not yet list the primary or other...

Not a problem... thanks for the feedback.

Nope... new columns always get added to the "end" of the table if you use just an ALTER.

However, if you go into Enterprise Manager to design the table (add the...

By the way (drum roll, please), congrats on the more than 7000 posts you've made

True enough... you won't be making a view out of it, for sure

Bingo!!

Yep... and you've nailed the key to it... exclusive access... now, what table(s) will a developer ALWAYS have exclusive access to?

Yap... we've all written "those"... see the update I just posted to my previous message...

Sure, Remi... thanks for the interest...

Personally, I think triangular joins should never be used because it's an absolutely insane form of RBAR (a "Modenism" for "Row By Agonizing Row").  Here's an example...

X/2 records is the difference

Not sure why Mark thinks one is necessary here even with his latest explanation.  Still trying to figure it...

I guess I don't have enough information... first, I'm not sure why you need this...

join Number_list n

on n.number < t.Person_count --This makes a triangular join!!!

WHERE  n.number < @Max_person_count

Second, are...

Richard,

Each instance of CASE must have an END...  You have 3 instances of CASE but only 1 END.  That would be the problem.

However, the other guys are right... in this...