Viewing 15 posts - 55,546 through 55,560 (of 59,098 total)
Rom Beng,
Something like this should do it for you... read the embedded comments for an explanation, please... I did not use your given table structures... this is all based on...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 4, 2007 at 9:42 am
Care to share the solution?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 4, 2007 at 8:54 am
What was the question???? And, if you solved it, what was the answer???
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2007 at 8:26 pm
You bet... thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2007 at 8:01 pm
That's basically what Tomm's solution does ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2007 at 7:59 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2007 at 7:39 pm
Aw... I know what to do with this... Bankers Rounding! Helps the 15's even out ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2007 at 7:29 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2007 at 7:27 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2007 at 6:30 pm
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.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2007 at 6:21 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2007 at 6:18 pm
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. ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2007 at 6:05 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2007 at 5:13 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2007 at 5:07 pm
| A relational database doesn't really do random well... If you want truly random results from one query to... |
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2007 at 4:59 pm
Viewing 15 posts - 55,546 through 55,560 (of 59,098 total)