|
Home > Archive > SQL Anywhere database > May 2005 > proxy table, stored procedure
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
proxy table, stored procedure
|
|
|
| I have a proxy table attached to a SQL Server database by
use of a remote server using an ODBC connection. I can
select, update, insert, delete from this proxy table.
My goal is to (by use of stored procedure) select data from
these proxy tables and transfer the data to a local table in
my Sybase db, which it will be its final resting place.
When I execute the stored procedure, I am getting an error
message...
"Could not execute statement. Correlation name 'tbxhdr' not
found
SQLCODE=-142, ODBC 3 State="42S02"
Line 3, column 1"
Am I doing something wrong?
| |
| David Kerber 2005-05-17, 8:23 pm |
| In article <428a3b96.7ffb.1681692777@sybase.com>, Steve says...
> I have a proxy table attached to a SQL Server database by
> use of a remote server using an ODBC connection. I can
> select, update, insert, delete from this proxy table.
>
> My goal is to (by use of stored procedure) select data from
> these proxy tables and transfer the data to a local table in
> my Sybase db, which it will be its final resting place.
>
> When I execute the stored procedure, I am getting an error
> message...
>
> "Could not execute statement. Correlation name 'tbxhdr' not
> found
> SQLCODE=-142, ODBC 3 State="42S02"
> Line 3, column 1"
>
> Am I doing something wrong?
You must be, or you wouldn't be getting an error <grin>. That looks
like an error (maybe just a typo?) in your SP code. Show us the code
for the SP and the proxy table, and we might be able to help you isolate
it.
--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).
| |
| Breck Carter [TeamSybase] 2005-05-17, 8:23 pm |
| Yes, something is wrong... please show us the code :)
Breck
On 17 May 2005 11:44:42 -0700, Steve wrote:
>I have a proxy table attached to a SQL Server database by
>use of a remote server using an ODBC connection. I can
>select, update, insert, delete from this proxy table.
>
>My goal is to (by use of stored procedure) select data from
>these proxy tables and transfer the data to a local table in
>my Sybase db, which it will be its final resting place.
>
>When I execute the stored procedure, I am getting an error
>message...
>
>"Could not execute statement. Correlation name 'tbxhdr' not
>found
>SQLCODE=-142, ODBC 3 State="42S02"
>Line 3, column 1"
>
>Am I doing something wrong?
--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
| |
|
| Thanks...
> That looks like an error (maybe just a typo?) in your SP
> code. Show us the code for the SP and the proxy table,
> and we might be able to help you isolate it.
This is all I needed. I was more concerned that I can
perform this task the way I set it up. I think I found my
mistake in my code.... for now!
> In article <428a3b96.7ffb.1681692777@sybase.com>, Steve
>
> You must be, or you wouldn't be getting an error <grin>.
> That looks like an error (maybe just a typo?) in your SP
> code. Show us the code for the SP and the proxy table,
> and we might be able to help you isolate it.
>
> --
> Remove the ns_ from if replying by e-mail (but keep posts
> in the newsgroups if possible).
| |
| David Kerber 2005-05-17, 8:23 pm |
| In article <428a4804.4963.1681692777@sybase.com>, Steve says...
> Thanks...
>
>
> This is all I needed. I was more concerned that I can
> perform this task the way I set it up. I think I found my
> mistake in my code.... for now!
Yes, in general you should be able to do this kind of thing. I have one
piece of an app where I actually create the remote server and proxy
tables on the fly, make my updates, and then drop them again.
....
--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).
|
|
|
|
|