Viewing 15 posts - 42,271 through 42,285 (of 59,102 total)
cos_ta393 (8/19/2009)
IT WORKS!!!!!! Thanks a million for your assistance; it is very much appreciated. Also my apology for giving Lutz credit for your articles and I want you to...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 19, 2009 at 6:33 pm
GilaMonster (8/19/2009)
I scored best whiteboard session of the entire conference and best breakout session of...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 19, 2009 at 4:54 pm
dsteinschneider (8/4/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2009 at 8:25 pm
Ack... sorry... lost track of this one. Thanks for taking the time to post the reason for this. Legacy code is always a bugger.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2009 at 8:19 pm
Heh... stiffed again. As soon as they get their answer, they're off until the next time they need help.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2009 at 7:11 pm
Kit G (8/18/2009)
Jeff Moden (8/17/2009)[/b]
I guess that's part of what I mean... why wouldn't you correct the original blog?
I can think of one other reason not to edit the original...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2009 at 6:43 pm
Grant Fritchey (8/18/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2009 at 6:32 pm
Jeff Moden (8/18/2009)
cos_ta393 (8/18/2009)
3) Finally I reviewed Lutz's articles but this solution will be implemented against a 2000 engineThanks,
Heh... then the crosstab solution in both articles is perfect for you.
Thanks...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2009 at 6:19 pm
lmu92 (8/18/2009)
b) the linked article I pointed you at is not mine so I don't deserve any credits for it... (right, Jeff? )
Actually, some good credit is due... you...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2009 at 5:56 pm
cos_ta393 (8/18/2009)
3) Finally I reviewed Lutz's articles but this solution will be implemented against a 2000 engineThanks,
Heh... then the crosstab solution in both articles is perfect for you.
Thanks for answering...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2009 at 5:55 pm
cos_ta393 (8/18/2009)
Thanks for pointing that out. The layout should look like:
cusid name product1 status ...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2009 at 11:15 am
paul.knibbs (8/18/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2009 at 7:43 am
jeff (8/17/2009)
Jeff Moden - Oops, sorry, I thought you were being frivolous before; was kind of hard to tell what you meant. Thanks! I will check that out.
Heh......
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2009 at 9:00 pm
Grant Fritchey (8/17/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2009 at 8:53 pm
Just a hint...
SELECT -1.06E+3, ROUND(-1056,-ROUND(LOG(ABS(1.06E+3))/LOG(10),0,1)+2)
Of course, if you use that in a WHERE clause, there's no way an Index Seek will ever occur. The formula is deterministic so...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2009 at 8:49 pm
Viewing 15 posts - 42,271 through 42,285 (of 59,102 total)