Care to share the solution?

What was the question???? And, if you solved it, what was the answer???

You bet... thank you for the feedback.

That's basically what Tomm's solution does

Heck... I know that... but now you have code to maintain in two places if the requirement for the schema of the temp table changes.  Yeah, I know... it's a...

Aw... I know what to do with this... Bankers Rounding!  Helps the 15's even out

Another analogy... ask the people that have suffered "brown lung" disease or sudden near death or Anaphylactic shock due to contact with the oils from certain woods what they...

I'm confused... you post a SELECT and call it an UPDATE (I have the following update statement that joins to a view).  You want to limit to "just those for postal...

You can simply remove the join that's automatically created between SysID's in EM in the design mode.  Then, create whatever view you want using your own joins.

Ummm... Not quite true unless you know how to use IndexProperty to identify if it's a primary key or not... If you know a way to do that, I'm all...

Stephen,

I agree... you did it correctly and the tool is wrong.  Obviously, the tool doesn't know what the heck a cross-reference table is. 

We had the same problem where I work.  The REAL problem is the sequence table... the code called SPGetNextSequence can only return one sequence number (think GET NextID).  This will...

What makes it questionable (in my feeble mind) is the idea of code reuse... those other stored procedures rely on the temp table being there when they start... you can't...

And, what is the Primary Key of the table?