Re: .1 in Providername

From: Viatcheslav V. Vassiliev (support_at_oledbdirect.com)
Date: 02/25/05

  • Next message: Bas van Beek: "Re: Not enough Parameters?" 
    Date: Sat, 26 Feb 2005 01:14:49 +0300

    .1 is version number. SQLOLEDB uses latest version of provider, SQLOLEDB.1 -
    version 1 (it is not related to MDAC version). Because for Yukon (MS SQL
    Server 2005) there will be new OLEDB provider (SQLNCLI), it seems that .1
    will be the last version for SQLOLEDB. It is better to show on MS Office -
    Word.Application.11 is for Office 2003, just Word.Application - for latest
    installed Word, i.e. if you have Office 2000, you will be able to create
    object Word.Application but not Word.Application.11.

    Both SQLOLEDB and SQLOLEDB.1 are ProgID, so setting wrong number (value that
    is not in HKCR\SQLOLEDB.X in registry) will not work.

    //------------------------------------------
    Regards,
    Vassiliev V. V.
    http://www.managed-vcl.com - using .Net objects in Delphi for Win32 +
    ADO.Net
    http://www.oledbdirect.com - The fastest way to access MS SQL Server,
    MS Jet (Access) and Interbase (through OLEDB)

    "Stefan Westner" <s@westner.de> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ ÓÌÅÄÕÀÝÅÅ:
    news:421f9fc9$1@newsgroups.borland.com...
    > Hello Dennis,
    >
    > thanks. Further question: if I build the connection-string dynamically
    > in my datamodule I have to set the provider. If I want to use
    > SQL-Server I set SQLOLEDB. Do I need to add the .1 and is the .1 the
    > same on every computer or could this vary and if this could vary is it
    > a problem to set it to the wrong value or where should I get the right
    > value?
    >
    > Stefan
    >
    > Dennis Passmore wrote:
    >
    >> The ".1" is actually a part of the actual 'ProgID' value in the
    >> registry for that provider. Just do a search in regedit for
    >> 'SQLOLEDB.1'
    >>
    >>
    >> Dennis Passmore
    >> Ultimate Software, Inc.
    >

  • Next message: Bas van Beek: "Re: Not enough Parameters?"

    Relevant Pages

    • Re-4: Codepage-Probleme
      ... Versuch mal mit OLE DB für SQL Server ist ... > Der Microsoftr OLE DB Provider für SQL Server, SQLOLEDB, ... > einer Verbindungszeichenfolge gesetzt werden. ...
      (microsoft.public.de.sqlserver)
    • Re: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]The operation could
      ... JDBC to run a query against a linked server that uses our SQLOLEDB provider. ... I would suggest narrowing down the troubleshooting and trying your query through Query Analyzer. ...
      (microsoft.public.sqlserver.jdbcdriver)
    • Re: !!
      ... I installed sql 2005 compact Edition. ... Everytime I try to connect, iot asks me for provider, a server and a database. ... SQL Server 2005 Compact Edition. ...
      (microsoft.public.vb.general.discussion)
    • Connecting to remote SQL database on the sbs does not work but will work on the workstations
      ... Hello we are soon creating a new system that will require our sql ... database on our websites dedicated server. ... An error has occurred while establishing a connection to the server. ... (provider: TCP Provider, error: 0 - A socket operation ...
      (microsoft.public.windows.server.sbs)
    • Re: Re-2: Codepage-Probleme
      ... Microsoft OLE DB Provider für SQL Server ... Der Microsoft® OLE DB Provider für SQL Server, SQLOLEDB, ...
      (microsoft.public.de.sqlserver)