Re: ADODB.Connection funkiness
- From: "Daniel Crichton" <msnews@xxxxxxxxxxxxxxxx>
- Date: Fri, 12 May 2006 15:02:17 +0100
NMAv wrote on Fri, 12 May 2006 06:43:01 -0700:
Thank you for the reply.
I understand that GO is not a recognized TSQL statement, but rather a
isql/osql/query analyzer command. However, it seems that ADO is able to
deal with the GO statement just fine provided the the preceeding statement
do not end with a semi colon. This seems bizarre to me and I'm hoping
there is a simple explanation/fix short of just remove the GOs or the semi
colons.
Well, I just tested with ADO 2.8 on my PC here against a SQL Server 2005
database and GO isn't accepted at all - I get "Incorrect syntax near 'GO'"
whether a semi-colon is there or not.
Dan
.
- References:
- Re: ADODB.Connection funkiness
- From: Daniel Crichton
- Re: ADODB.Connection funkiness
- Prev by Date: Re: ADO.NET adapter save DataSet
- Next by Date: Re: ADODB.Connection funkiness
- Previous by thread: Re: ADODB.Connection funkiness
- Next by thread: Re: ADODB.Connection funkiness
- Index(es):