Since it is double posted, I'll say it again here for clarity.

What's the point?

That's nice. What's the point?

Something like this?

declare @TestDate datetime;

set @TestDate = '2009-12-19';

select dateadd(wk,datediff(wk,0,@TestDate + 1),-9),dateadd(wk,datediff(wk,0,@TestDate + 1),-3)

set @TestDate = '2009-12-24';

select dateadd(wk,datediff(wk,0,@TestDate + 1),-9),dateadd(wk,datediff(wk,0,@TestDate + 1),-3)

Cute, Alvin. Just...

Something changed between the 16th and the 17th. Working code doesn't suddenly stop working for no reason. Something in the environment, the data, or the code changed. ...

Job worked on the 16th, failed on the 17th....

From what I can tell, haven't done it myself as we are running x64 SQL on our x64 OS's, is the 32 bit SQL will run just fine on x64...

So, Steve, going tell us about the upgrade?

Knowing what I know (and don't as well), I'd prefer to keep away from creating dynamic sql in the application. I would prefer to use stored procedures to encapsulate...

Properly used CTE's are well worth considering. They can help with the development of complex queries, and if you have section of code that would use the same...

Sample data, expected results?? The more you do to help u help you, the better answers you will get.

That can do it. Let us know if changing to a domain accout solves the problem.

Blind I may be, where are the trigger(s), sample data, expected results after processing?

Does this batch file you are trying to run on a remote server, run ON the remote server or just FROM the remote server?

sureshdeenu (12/18/2009)

---

Declare @UpdateText as VarChar(2000)

Set @UpdateText =

'Update GeStatus ' +

'Set ChangedRecordX = ''x'', ' +

'[' + RTrim(@ChangedFieldName) +'] = ''x'' ' +

'Where Client = ''' + RTrim(@Client) + '''...