CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums Developer.com
Results 1 to 7 of 7

Thread: MSDN: Documentation issue

  1. #1
    Join Date
    Aug 2002
    Posts
    743

    MSDN: Documentation issue

    Hi, ALL,
    Could someone lease explain why some pages in MS documentation do not match when they should?

    1. Page 1 at https://docs.microsoft.com/en-us/sql...l-server-ver15
    2. Page 2 at https://docs.microsoft.com/en-us/sql...l-server-ver15.

    Those 2 pages should directly correspond with the column 1 in the first page and column 2 in the second.

    However in reality there some rows in the table on page 1 that does not have corresponding row on page 2.

    And this is not specific to this.


    Or maybe I'm looking at it wrong and they should correspond by different columns in the tables?

    Thank you.

  2. #2
    VictorN's Avatar
    VictorN is offline Super Moderator Power Poster
    Join Date
    Jan 2003
    Location
    Hanover Germany
    Posts
    19,980

    Re: MSDN: Documentation issue

    I guess the reason is: SQL Data Types are not the same as ODBC C data types:
    Each DBMS defines its own SQL types. Each ODBC driver exposes only those SQL data types that the associated DBMS defines. Information about how a driver maps DBMS SQL types to the ODBC-defined SQL type identifiers and how a driver maps DBMS SQL types to its own driver-specific SQL type identifiers is returned through a call to SQLGetTypeInfo. ...
    Victor Nijegorodov

  3. #3
    Arjay's Avatar
    Arjay is offline Moderator / EX MS MVP Power Poster
    Join Date
    Aug 2004
    Posts
    13,477

    Re: MSDN: Documentation issue

    People still use ODBC?

  4. #4
    VictorN's Avatar
    VictorN is offline Super Moderator Power Poster
    Join Date
    Jan 2003
    Location
    Hanover Germany
    Posts
    19,980

    Re: MSDN: Documentation issue

    Quote Originally Posted by Arjay View Post
    People still use ODBC?
    Yes. For example our company still uses ODBC (the old MFC CDatabase and CRecordset classes).
    Unfortunately...
    I hate odbc, but I must use it almost everywhere in code.
    Victor Nijegorodov

  5. #5
    GCDEF is offline Elite Member Power Poster
    Join Date
    Nov 2003
    Location
    Florida
    Posts
    12,620

    Re: MSDN: Documentation issue

    Quote Originally Posted by Arjay View Post
    People still use ODBC?
    It works for me

  6. #6
    Arjay's Avatar
    Arjay is offline Moderator / EX MS MVP Power Poster
    Join Date
    Aug 2004
    Posts
    13,477

    Re: MSDN: Documentation issue

    For older technologies, the ATL OLEDB Consumer classes are an order of magnitude improvement over the MFC db classes. They're lighter weight, easier to modify for schema changes, support multiple db types, and work well inside an MFC app. They are definitely worth a look.

  7. #7
    VictorN's Avatar
    VictorN is offline Super Moderator Power Poster
    Join Date
    Jan 2003
    Location
    Hanover Germany
    Posts
    19,980

    Re: MSDN: Documentation issue

    Quote Originally Posted by Arjay View Post
    For older technologies, the ATL OLEDB Consumer classes are an order of magnitude improvement over the MFC db classes. They're lighter weight, easier to modify for schema changes, support multiple db types, and work well inside an MFC app. They are definitely worth a look.
    Arjay, I'm not who makes a decision which classes to use.
    I'd better use the ADO, but I work in this company only 3.5 years while they use ODBS since 1998 or earlier!
    Victor Nijegorodov

Posting Permissions

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


Windows Mobile Development Center


Click Here to Expand Forum to Full Width




On-Demand Webinars (sponsored)