Heh, so the "local settings" were... a different time. :blush:

Interesting. Not sure what local settings would cause something like that. You could probably get rid of it with a REPLACE(x,' ',''), but that seems a bit wasteful.

Or this one:

[font="Courier New"]DECLARE @Tests TABLE(

CourseNum  INT,

Grade      CHAR(1))

INSERT INTO @Tests(CourseNum, Grade)

SELECT 0500300,            'A' UNION ALL

SELECT 0500300,            'B' UNION ALL

SELECT 0500300,            'A' UNION ALL

SELECT 0500300,            'C' UNION ALL

SELECT 0600000,            'A' UNION ALL

SELECT 0600000,            'C'

SELECT

  ...

Not sure what your question is. When I run your strings, I get this:

10 142210144

What are you getting?

Using a 2 digit year for DOB seems like it could cause you problems down the road, as people can live to be over 100 (and a few other scenarios...

Oh where to start.

First. Do not create new threads with the same question in them. It splits replies, confuses things and just generally annoys people.

Second. You still...

Actually, my first post isn't necessarily true. You may be able to restore the db and the transaction logs up to the point of your bad update query if...

If you didn't nest your update in a transaction, and you don't have implicit transactions turned on for your connection... then no.

Restore your database with a different name,...

LOL. Well... they DID use a parameter.:hehe:

You can't pass a list like that directly. You can do it with either dynamic SQL, or splitting that comma delimited list. There are advantages and disadvantages to...

@Barry:

UGH. I thought about rounding like 3 times, but kept looking at his data and thinking "It's all integers, shouldn't be an issue." Well, it's not. Until...

Is that query the only thing that is in your query window? Sometimes in cases like this it's executing something else that you're not intending to execute which is...

You have to alias the table variable and use that in your declaration.

Use this instead:

UPDATE @x_job_cash_flow

SET inv_payment_amt = PS.inv_payment_amt

FROM @x_job_cash_flow CF

INNER JOIN @x_ap_payment_summary PS ON CF.company_code...

Something tells me you didn't read the article.

My guess is that the ASP page is actually running your query twice. I've seen this before. I haven't done much research into why it happens, but I've...