Re: ADODB.Connection funkiness
- From: "Daniel Crichton" <msnews@xxxxxxxxxxxxxxxx>
- Date: Fri, 12 May 2006 08:54:54 +0100
NMAv wrote on Thu, 11 May 2006 23:03:01 -0700:
I've got an asp page that is used to update multiple databases residing on
multiple servers. We select which server/db combination to update and
submit and the all the SQL statements we've typed into the form are
processed. The problem is if we have something like this:
Insert into dumm(DUMMY1, DUMMY2)
SELECT 'XYZ','ABC';
GO
Insert into dumm(DUMMY1, DUMMY2)
SELECT 'PDQ,'DEF';
GO
ADO seems to freak out with the semicolon followed by the GO. If I remove
the semi colon the statement executes. If I remove the GO, the statements
execute. It is just when they are together that there is a problem. Why
is this? It doesn't happen in Query Analyzer. And more importantly is
there a fix or workaround? The SQL is created by a different process and
can be very large so doing away with the semicolon or the GO statement
would be difficult.
Looking to help, a direction, an intelligent explanation. Please.
GO is a batch delimiter in Query Analyzer, outside of that it has no
meaning. You can change it to something else in QA if you like. Just leave
out the GO's and it'll work as expected.
Dan
.
- Prev by Date: Re: Looping thru an ADO disconnected recordset - while/wend not workin
- Next by Date: ADO.NET adapter save DataSet
- Previous by thread: Re: Looping thru an ADO disconnected recordset - while/wend not workin
- Next by thread: Re: ADODB.Connection funkiness
- Index(es):
Relevant Pages
|
