Linked View to SQL Server DB

I am using a linked view created in the SQL Server database. However, when
I
run it I get the following error.
ODBC--call failed.
[Microsoft][ODBC SQL Server Driver]Invalid character value for cast
specification (#0)
The help for this message indicates that it may be a network problem.
However, all other tables and views run correctly. This is the only one tha
t
fails. I have relinked, I have removed and recreated the link, and still
this one table view fails.
Any suggestions will be appreciated.Not sure what your other data source is but it looks like a
data type translation issue, not necessarily a network
issue. Try updating the ODBC driver - older versions don't
support newer data types.
If you are referring to something you are doing in MS
Access, you need to make sure to update your Jet drivers as
well.
-Sue
On Wed, 5 Jul 2006 07:23:02 -0700, Outdone
<Outdone@.discussions.microsoft.com> wrote:

>I am using a linked view created in the SQL Server database. However, when
I
>run it I get the following error.
>ODBC--call failed.
>[Microsoft][ODBC SQL Server Driver]Invalid character value for cast
>specification (#0)
>The help for this message indicates that it may be a network problem.
>However, all other tables and views run correctly. This is the only one th
at
>fails. I have relinked, I have removed and recreated the link, and still
>this one table view fails.
>Any suggestions will be appreciated.|||I have a similar problem (and I'm new to SQL Server). I created a view in
SQL Server. I assigned select permissions for a user ID on that view. I
then created an odbc connection so I could link that view in my Access
database. When I try to open the view, I get the 'ODBC--call failed' error.
I can access all the other linked tables within Access. Is there a problem
with the permissions set on the view, or is it an odbc problem?
Thanks,
Melanie
"Sue Hoegemeier" wrote:

> Not sure what your other data source is but it looks like a
> data type translation issue, not necessarily a network
> issue. Try updating the ODBC driver - older versions don't
> support newer data types.
> If you are referring to something you are doing in MS
> Access, you need to make sure to update your Jet drivers as
> well.
> -Sue
> On Wed, 5 Jul 2006 07:23:02 -0700, Outdone
> <Outdone@.discussions.microsoft.com> wrote:
>
>|||Really can't say. ODBC call failed is just a generic error
message. You could try turning on ODBC tracing on the client
to try to get more information on the error. You would want
to make sure to turn it back off after you get the error as
it will really slow things down.
To turn on tracing, go to the ODBC Data Source Administrator
applet and go to the tracing tab. Just click on start
tracing now and note the location for the trace file. After
you hit the error, go back and click on the stop tracing now
button. Then you can go to the trace file and see what other
information you can get out of the trace file.
-Sue
On Wed, 5 Jul 2006 13:39:01 -0700, Melanie O
<MelanieO@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I have a similar problem (and I'm new to SQL Server). I created a view in
>SQL Server. I assigned select permissions for a user ID on that view. I
>then created an odbc connection so I could link that view in my Access
>database. When I try to open the view, I get the 'ODBC--call failed' error
.
>I can access all the other linked tables within Access. Is there a problem
>with the permissions set on the view, or is it an odbc problem?
>Thanks,
>Melanie
>"Sue Hoegemeier" wrote:
>