I asked this question on 3/25/03 as 'PROBLEM UPDATING SQLSERVER VIA REMOTE VIEW/ODBC' and got no response.
I'd like to try again.
I have reviewed the discussion on lashwarj's question on 6/3/03. The sqlconnect/sqlmoreresults solution doesn't apply since I'm not using sqlexec to access the SQL SERVER table; I'm opening a remote view ('use gleads_vw').
I know what's happening; a connection is made with the sql server and a cursor is being generated;
THE PROBLEM: before all the records can be fetched my program has moved on and it is trying to update the remote table.
MY BANDAID has been to put a wait window before the first update and delay 5 seconds. This works most of the time unless the internet traffic is too slow or the table being fetched is to big. Then I get the "connection is busy" error; the connection is still being used to build the cursor.
WHEN USING A REMOTE VIEW IS THERE ANY WAY TO TEST WHETHER THE FETCHING IS COMPLETE; something like sqlmoreresults???
Is it necessary to scrap the remote view approach and use sqlexec instead? I'd rather not!
I'd like to try again.
I have reviewed the discussion on lashwarj's question on 6/3/03. The sqlconnect/sqlmoreresults solution doesn't apply since I'm not using sqlexec to access the SQL SERVER table; I'm opening a remote view ('use gleads_vw').
I know what's happening; a connection is made with the sql server and a cursor is being generated;
THE PROBLEM: before all the records can be fetched my program has moved on and it is trying to update the remote table.
MY BANDAID has been to put a wait window before the first update and delay 5 seconds. This works most of the time unless the internet traffic is too slow or the table being fetched is to big. Then I get the "connection is busy" error; the connection is still being used to build the cursor.
WHEN USING A REMOTE VIEW IS THERE ANY WAY TO TEST WHETHER THE FETCHING IS COMPLETE; something like sqlmoreresults???
Is it necessary to scrap the remote view approach and use sqlexec instead? I'd rather not!