Then, you can do one of two things...

1.  Import to a 3 column staging table (where you can also validate the data before making it live, good safeguard) and transfer...

Oh, I agree... I'm lucky enough to have a similar situation.

Just wanted everyone to know the implicit "dots" work the same way (month before day) on certain servers and not...

Yeah, shame on me... I keep forgetting about that... On other servers, particularly those outside the U.S.A., the reverse failure would be true...

Jonathon

I agree with Kenneth... proper syntax calls for the column name to be followed with either a comma, an AS with an alias followed by a comma, or an alias...

Much better... but won't work in SQL Server 2000 which is what this forum is...

Heh... or just pay attention to what you're doing   Either way, a trip to the estimated execution plan probably would have shown the...

Glad it helped...

Any chance of you posting your final code?

Your solution can not work without the numbers table... at least a link would have been nice...

Steal from the "sp_" code...

Sure... when you first create a server instance, they are not there.  They only appear when something first needs them... then, they persist.

Um... be careful in that assumption... while this works...

DECLARE @SomeDate DATETIME

SET @SomeDate = '05.24.2007'

PRINT @SomeDate

...this will not...

DECLARE @SomeDate DATETIME

SET @SomeDate = '24.05.2007'

PRINT @SomeDate

...because the implicit format is understood to be mm.dd.yyyy.

Still worth it... maybe someone else can get a leg up on things if they manage to find it...

"Error like this object already exists?"  What on Earth are you doing with the Dynamic SQL?

What... and miss out on all that high-class entertainment?