System.Data.SQL v. System.Data.ADO

Results 1 to 2 of 2

Thread: System.Data.SQL v. System.Data.ADO

  1. #1
    Join Date
    Dec 1969

    Default System.Data.SQL v. System.Data.ADO

    Besides the fact that one access SQL Server and the other is for other ODBC data sources, is there any syntactical difference besides the actual connection string to connect to the database?<BR><BR>For example, if I want to do this, and it works with Access, will it work in SQL Server with a simple find/replace for ADO with SQL?<BR><BR>Dim myConnection as ADOConnection <BR>Dim myCommand as ADOCommand <BR><BR>myConnection = whatever<BR><BR>myCommand = new ADOCommand("INSERT into friends (firstNAME,lastname) VALUES (&#039;David&#039;,&#039;Johnson&#039;)", myConnection) <BR>myConnection.Open() <BR>myCommand.Execute() <BR>myConnection.Close()

  2. #2
    Join Date
    Dec 1969

    Default Nope...

    No syntactical difference (other than the ADO prefix being swapped with the SQL prefix, or vice versa). The SQL classes offer increased performance with SQL Server 7.0 and up, though, implementing a protocol that talks directly with SQL Server instead of using the OLE-DB provider.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts