Viewing 15 posts - 55,516 through 55,530 (of 59,072 total)
Heh... the reason why you didn't find it in Books Online is because formatting dates for a GUI in SQL is a really bad idea for about a thousand reasons,...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 4, 2007 at 2:32 pm
Ok... let's say that's correct for a minute... what does something like the following cost in the short term? Nothing... schedule met... everyone was happy...
What's it costing them now? Somebody was...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 4, 2007 at 10:15 am
Well kinda...
Change the FK's to "CASCADE ON DELETE" and then you only need to delete from one table ![]()
Lookup "cascading referential integrity constraints" in...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 4, 2007 at 10:11 am
P.S. If you do decide to go the temp table route as I suggested, then adding the appropriate indexes and a primary key on the temp table may help speed things...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 4, 2007 at 10:06 am
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
Viewing 15 posts - 55,516 through 55,530 (of 59,072 total)