Re: ADODB.Connection funkiness
- From: "Daniel Crichton" <msnews@xxxxxxxxxxxxxxxx>
- Date: Fri, 12 May 2006 16:30:17 +0100
Just to check, I tested with SQL Server 2000 and SQL Server 7, and got the
same error message.
Dan
NMAv wrote on Fri, 12 May 2006 07:58:02 -0700:
Odd, "I've not tried on SQL2k5 but we are migrating that way so I might as
well just get rid of them. I'm going to parse the GO's out of the sql
statement and be done with it.
Thanks for your time.
"Daniel Crichton" wrote:
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
- From: Daniel Crichton
- Re: ADODB.Connection funkiness
- Prev by Date: Re: ADODB.Connection funkiness
- Next by Date: Re: Looping thru an ADO disconnected recordset - while/wend not wo
- Previous by thread: Re: ADODB.Connection funkiness
- Next by thread: ADO.NET adapter save DataSet
- Index(es):
Relevant Pages
|
|