Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From: "Bob Barrows" <reb01501@NOSPAMyahoo.com>
Newsgroups: comp.databases.ms-sqlserver
Subject: Re: Problem with casting value under 64-bit sql server 2005 vs under 32-bit sql server 2005
Date: Fri, 12 Aug 2011 16:56:01 -0400
Organization: A noiseless patient Spider
Lines: 28
Message-ID: <j243v9$ui4$1@dont-email.me>
References: <bc35893b-4e20-4fe7-81b3-1472057cfb8d@u12g2000prc.googlegroups.com> <j23t1o$cls$1@dont-email.me> <e6b3dbb8-b88b-40d4-bb6a-763a831459ef@j14g2000prh.googlegroups.com>
Injection-Date: Fri, 12 Aug 2011 20:55:05 +0000 (UTC)
Injection-Info: mx04.eternal-september.org; posting-host="inlgCTpOMxujS+VHkVo6dA"; logging-data="31300"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18/6plIO4b3ThDEwj09QPPNDRZWoWtfdL8="
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-RFC2646: Format=Flowed; Original
X-Antivirus-Status: Clean
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-Antivirus: avast! (VPS 110812-0, 08/12/2011), Outbound message
Cancel-Lock: sha1:VIG0Anu7jyYUeUicFH2BwO64Ork=
X-Priority: 3
X-MSMail-Priority: Normal
Xref: x330-a1.tempe.blueboxinc.net comp.databases.ms-sqlserver:596

xo wrote:
<snip>
> The error seems to be caused by the last line.  Add'l info - FLODS_ID
> is (PK, numeric (18,0), not null) and OBJECT_ID (varchar(80), null)
>
> Below is the sql -
>
<snip>
> Thanks in advance

Thanks for the attempt to provide extra information. Unfortunately it was 
both too much and not enough information.
Please provide:
1. A CREATE TABLE script to allow us to create a table with only the 
relevant columns. Do not include any columns that are not needed to recreate 
the symptom.
2. A script to insert some sample data into the table. The sample data 
should include the row that causes the error message.
3. The sql statement that uses the test table to reproduce the symptom

This of course will require you to find the row(s) containing the data that 
causes the error. Doing so might lead you to the answer to your question. I 
suggest you remove tables and columns from the sql you provided until you 
can run it without error. Then add back in a column/table at a time until 
the error does occur. Then try limiting the results using a WHERE clause 
until you identify the row(s) containing the problem data.