×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hi Dave,
This line looks suspicious to me:
and A.artxyr = 2011 || :RPTTXYR
Are you truly trying to concatenate a number (2011) to a variable? If
so, SQL will have to implicitly do some casting to make it work, which
might be where the issue is.
The other thing that comes to mind is the FETCH statement -- I'm mainly
suspicious of the FETCH because you say it works in iNav, which implies
the issue is something you wouldn't have done in iNav (such as a fetch)
It's possible that SQL is implicitly casting between a numeric/character
data type in the fetch... maybe because the receiver data type doesn't
match the database data type. Worth checking into...
-SK
On 5/29/2012 4:49 PM, Dave Boettcher wrote:
Kurt, Good guess. I still receive the error either way.
Jonathan , You're right it was defined as character. I had great
hopes for this one but still receive the error. I should only need
the coalesce on the Declare statement not the fetch, right?
Tom, the phones are signed numeric and so I tried the + signs. It
seems that a zero shouldn't need to have a sign but it was worth a
shot.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
