Viewing 15 posts - 57,541 through 57,555 (of 59,098 total)
Greg,
It would appear that your TimeIn column could have the following formats...
6:15 a.m.
12:15 p.m.
6:15 p.m.
12:15 a.m.
The periods in the "a.m." and "p.m." could make this a bugger to convert. Even...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 1, 2006 at 9:20 pm
The way you indent on this forum is to use leading spaces or use the "Increase Indent" tool at the top of the message box when you are creating your...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 1, 2006 at 8:36 pm
Ok, Lisa... you just assumed that I knew you were talking about the "other" code in your rule of thumb and I thought you were talking about the code I submitted...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 1, 2006 at 1:04 pm
1. The order will almost always be determined externally to this expression anyway, since unless you can guarantee < 12 months and all in the same calendar year you might...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 1, 2006 at 11:28 am
Ian,
Nice job at producing the return that the original poster actually asked for... there is one little problem... you cannot include the ELSE clause that you have or you get...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 1, 2006 at 11:01 am
Even though their occurance is really unacceptable, deadlocks are about as normal (I didn't say "as frequent") as regular locking anytime you have both a SELECT and an UPDATE in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 1, 2006 at 9:43 am
I'm thinking that formatting the message is much less important that formatting the code for readability...
It only took about ten minutes to...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 30, 2006 at 9:44 pm
Forgot something else... if you parameterize the table name for the small names table, you can pass a parameter to use different name tables... that will allow you some extreme...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 30, 2006 at 11:08 am
You might also want to remember that the minimum resolution for the DateTime data type is 3 milliseconds, not 2 as posted in the original code.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 30, 2006 at 10:20 am
It would appear that Isa want's to manufacture data (for test or otherwise) with a random number generator for the "Aro_ID" column.
Isa, one question that remains is "Can there be...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 30, 2006 at 10:13 am
OK, Bruce... here you go...
You were worried about the performance of a cross-tab (aggregate functions)... as some have suggested (especially Serqiy), that really shouldn't be a concern. I know... you've...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 30, 2006 at 9:30 am
Jun,
Crud... Dan's right... sorry we got off track...
To reiterate Dan's question, what should the output look like?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 30, 2006 at 5:50 am
That'll do... I was just worried about the fact that you said it uses "recursive search on Customer table". To me, recursion is when a proc or function calls itself......
--Jeff Moden
Change is inevitable... Change for the better is not.
September 29, 2006 at 7:56 am
That's why "trick" was in quotes ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 29, 2006 at 7:50 am
Unorthodox? If you think about it, the table structure is similar to that which XML offers (thought everyone but me loved XML
) but...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 29, 2006 at 7:48 am
Viewing 15 posts - 57,541 through 57,555 (of 59,098 total)