Re: D3 ODBC Problem
- From: "Mark Brown" <Mark_Brown@xxxxxxxxxxxxx>
- Date: Fri, 25 Jul 2008 14:07:01 -0700
"Tony Gravagno" <address.is.in.posts@xxxxxxxxxxxxxxxxxxxxxx> wrote in message news:fcck84hesns7f8ge13rfarmof6h098ep68@xxxxxxxxxx
Two comments.And I did write a program to comb the data and the data is clean.
removepleaseNebula-RnD.com/freeware/FIND.BAD.CHAR.TXT
D3 ODBC sucks
If I had said that, all hell would break loose. Suffice to say, you
know the solution I would propose.
T
Error messages from WinSQL are usually fairly accurate. If it says invalid data, it's probably invalid.
Poster said they scanned the data and there's no non-numeric data and that the field is normalized correctly in the SQL-CREATE-TABLE.
Next question is, what IS the data, exactly? Just because it's numeric, doesn't mean it's valid. If it's > 32K, then depending on which version of Windows O/S and which version of the SQL query, it may think an integer is 16bits and the data is invalid because of overflow.
--
Mark Brown
Sr. Software Engineer
Cancer Survivor
Drexel Management Svc Inc.
.
- Follow-Ups:
- Re: D3 ODBC Problem
- From: SteveS
- Re: D3 ODBC Problem
- References:
- D3 ODBC Problem
- From: SteveS
- Re: D3 ODBC Problem
- From: Frank Winans
- Re: D3 ODBC Problem
- From: SteveS
- Re: D3 ODBC Problem
- From: Tony Gravagno
- D3 ODBC Problem
- Prev by Date: Re: D3 ODBC Problem
- Next by Date: Re: D3 ODBC Problem
- Previous by thread: Re: D3 ODBC Problem
- Next by thread: Re: D3 ODBC Problem
- Index(es):
Relevant Pages
|