If you have a number of these kinds of calculations to make, you may want to make a calendar table.  Many different examples on SQLServerCentral... do a search.  Well worth...

You'll need one CASE per column returned... sounds long but runs very fast.

Heh... Even in the "higher priced spread" of Oracle, you have to TRUNC(somedate) to get the date with no time (midnight, really).

Both methods are identical in execution plan, performance, and resource usage.

Then you have to use Rob's method... triggers are absolutely oblivious as to what the source of information is so far as table name goes.

The "t" prefixed "indexes" are not "real" indexes... they are merely notations to the server that the table contains image or text datatypes...

Actually... there is a way... if you look in Books OnLine, the syntax for creating a stored procedure is....

CREATE PROC [ EDURE ] procedure_name [ ; number ]

    [...

--===== Create a test table to demo the problem with...

 SELECT '11AA' AS AccountID, CAST('01/01/2007' AS DATETIME) AS MyDateTime

   INTO #MyHead UNION ALL

 SELECT '11AA','01/02/2007' UNION ALL

 SELECT '11AA','01/03/2007' UNION ALL

 SELECT...

Not after a couple of days... unless you have a really good audit log.

's'ok... great minds think alike... I went a little nuts with the derived table thingy, though

Of course, if you used any one of a thousand or so set based solutions for this problem, you wouldn't have to worry about what a cursor does or doesn't...

01/01/1900 was also a Monday... kind of convenient, too, because the decimal equivelent for that date is "0".

Be a bit leary of queries that have an inequality in the WHERE clause especially when a self-join is also present as it may form a "triangular join" which is a...

You say you specifically want to use BCP... try BULK INSERT instead... lot's simpler than trying to get around the command shell thing.

Also, you can still use command shell as...

Hat's off to the "remaining partner"... well done, Mr. Jones!