Viewing 15 posts - 51,946 through 51,960 (of 59,091 total)
alorenzini (3/10/2008)
That worked fine. Thanks.
See above and reconsider how much hell you will go through if any of the dates ever come in with a time other than midnight... and...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 2:58 pm
Lynn Pettis (3/10/2008)
SELECT @startdate = CAST('2007' AS DATETIME)
SELECT @enddate = DATEADD(yy,1,CAST('2007' AS DATETIME)) - 1
I know why...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 2:56 pm
There are, of course, exceptions to every rule... but most people name a table after what a single row in the table holds. For example, the Customer table would...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 2:51 pm
First, I thought you said the "records" looked like this...
PunchIn, PunchOut, Break, PunchIn, Punchout.
Second... are your really happy with the solution? Try it with multiple days...
USE tempdb
go
Create Table Punches(empid...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 2:32 pm
dan (3/10/2008)
Some dates appear as '20080310' and others appear as '10/03/2008'.I have been asked to make all the dates appear consistently, as '20080310'. I've tried several variations of this:
You...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 2:06 pm
I have an OrderLookup table, where the PK is the PurchaseOrderID.
You actually named a table "OrderLookup" to hold Purchase Orders and gave it a Primary Key on a column called...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 1:49 pm
Will C2 Auditing help in this area?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 1:45 pm
Ummmm... let me get this straight... you got a job as a designer and you don't really know how to design?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 1:43 pm
SELECT CAST('2007' AS DATETIME)
SELECT DATEADD(yy,1,CAST('2007' AS DATETIME))
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 1:42 pm
Oral meds? Lucky... at least they weren't supositories 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 7:00 am
michael.esposito (3/10/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 6:54 am
Could be done in plain ol' T-SQL... but would require either a trip through xp_CmdShell or would need to be called externally in a batch file.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 6:50 am
Heh... yeah... I can see that... my question would be why? And if what you say were true, why list all of the users instead of just the most...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 6:42 am
Markus2006 (3/10/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 6:27 am
nicolas.pages (3/10/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 6:24 am
Viewing 15 posts - 51,946 through 51,960 (of 59,091 total)