Re: Samplclnt example in MDAC 2.8: My Story

See comments below...

"Warren Read" <wread@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:0V%23QaWg6FHA.1236@xxxxxxxxxxxxxxxxxxxxxxxx
> My understanding is that the samples worked with whatever version of
> Visual
> Studio shipped at the time. I'm not sure what it will take to get them to
> work with the latest releases of Visual Studio. Hopefully someone more
> knowledgeable will have an answer for you.

I made the necessary changes in the sample source files in order to compile
& link them with VS 2005, beta; it's not that difficult. The question I have
is executing the sample consumer application. I would like to hear if
anyone, regardless of their IDE, has successfully run the thing.

>
> I would like to know where you got the idea:
>
> Or maybe we're supposed to just keep using ODBC, which
> | although it has been officially deprecated, I'm told still performs
> better
> | than OLE DB.
>

I was incorrect when I stated that ODBC as a whole is deprecated. Only the
ODBC provider for OLE DB (MSDASQL) is deprecated; this information is taken
directly from the MDAC SDK 2.8 help file.

> I have been in the ODBC team for several years and haven't heard about it
> being deprecated. In fact, we're re-generating great support for future
> development of ODBC.

Sounds great. My question to you would be, why is Microsoft moving forward
with support of two different data access strategies, ODBC and OLE DB? It's
funny how Microsoft appears to be pushing OLE DB hard, yet people seem
reluctant to abandon ODBC, and again, I've heard from numerous sources that
ODBC still outperforms OLE DB, which is the newer technology (!).

This whole story began with my curiosity about OLE DB, and trying to explore
its utility. My exploration was quickly halted by the age & (in my opinion)
poor quality of the MDAC SDK's OLE DB sample source code. I reiterate my
question: if MS is serious about gaining a foothold with OLE DB, why does
their latest release of the MDAC SDK fail to compile with the most recent
IDE? Why are there no newer samples than those written circa 1998?

ODBC 1, OLE DB 0.

> Please let me know the source of this information so we can correct that
> source.
>
> ~Warren
>
> --------------------
> | From: "Michael Skelton" <mskelton@xxxxxxxxxxxxx>
> | Subject: Samplclnt example in MDAC 2.8: My Story
> | Date: Mon, 14 Nov 2005 12:45:13 -0500
> | Lines: 53
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
> | X-RFC2646: Format=Flowed; Original
> | Message-ID: <ODhqKNU6FHA.736@xxxxxxxxxxxxxxxxxxxx>
> | Newsgroups: microsoft.public.data.oledb
> | NNTP-Posting-Host: 12.29.236.34
> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
> | Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.data.oledb:22295
> | X-Tomcat-NG: microsoft.public.data.oledb
> |
> | Hello,
> |
> | I was wondering what people's experiences were in playing around with
> the
> | OLE DB provider/consumer sample that is included in the MDAC 2.8 SDK.
> So
> | far, it hasn't been great for me.
> |
> | I started off by attempting to build the sample provider DLL, which is
> the
> | what the consumer client uses to read the rudimentary .csv data file. In
> | terms of my development IDE, our company is playing around with the VS
> 2005
> | beta, so that is what I have installed on my machine. After I opened &
> | converted the project, I attempted to build it. I was met by a bevy of
> | compiler errors. Upon scrutinizing the errors, I realized that most of
> them
> | were probably a result of a relatively new compiler working with
> relatively
> | older C++ source files ;-). The source files did things like use the
> "old
> | style" C++ headers (e.g. <fstream.h> instead of <fstream>, which the
> | compiler apparently wouldn't tolerate. So, I worked through those
> issues,
> | and finally got the project to compile, but then it wouldn't link. Seems
> | that there were numerous duplicate symbols defined in a library that the
> | project depended on, I believe it was msdasc.dll (spelling?). Just as an
> | attempt to solve the problem, I removed this library from the project
> | dependencies, and it then succeeded in linking.
> |
> | Next I moved on to building the sample consumer application, samplclnt.
> This
> | project was much less difficult to build, in terms of the number of
> compiler
> | errors. So, I decided to try to run the application. The first roadblock
> I
> | ran into was that the .csv data file wasn't in the right place; I had to
> | copy that into the debug directory that the actual executable was
> written
> | to. Next, I realized that the sample application wasn't recognizing the
> | sample OLE DB provider. I guess the OLE DB provider information is
> resident
> | in the system registry. So, my solution here was to register the sample
> | provider DLL, using regsrv32. This successfully registered the sample
> OLE
> DB
> | provider, so the consumer application can now recognize & use it. So
> now,
> | when I run the sample app., I'm getting errors from some of the
> interface
> | implementations in the provider code. This is where I've pretty much
> ceased
> | to troubleshoot. From what I can tell, it looks like the provider might
> have
> | a bug in the low-level file IO routines used to read the .csv data file.
> I
> | was curious if others got the sample application to run, and if they
> also
> | encountered these errors.
> |
> | Overall, I was quite surprised that I needed to jump through these hoops
> | just to compile & link the sample code in the latest VS C++ environment.
> Is
> | there not a more recent distribution of the MDAC SDK sample files? I
> think
> | 2.8 is the most up-to-date version, but what I 'm looking for here is
> | something other than pre-standardized source code that was written
> before
> or
> | around 1998. One would be tempted to think that Microsoft might consider
> | distributing a more contemporary sample if they were serious about
> people
> | using OLE DB. Or maybe we're supposed to just keep using ODBC, which
> | although it has been officially deprecated, I'm told still performs
> better
> | than OLE DB.
> |
> | -Michael
> |
> |
> |
>


.

Relevant Pages

  • RE: Samplclnt example in MDAC 2.8: My Story
    ... | OLE DB provider/consumer sample that is included in the MDAC 2.8 SDK. ... | what the consumer client uses to read the rudimentary .csv data file. ... | compiler errors. ... | sample OLE DB provider. ...
    (microsoft.public.data.oledb)
  • OLE DB Provider for ODBC and Oracle
    ... I created a linked server for MS SQL Server 2005 Express to an Oracle ... database using the OLE DB Provider for ODBC. ... I'm using the OLE DB Provider for ODBC instead of the Oracle OLE DB ...
    (comp.databases.ms-sqlserver)
  • Re: Is there any (free!) ADO - OLE DB Provider for Lotus Notes?
    ... I know that I can use OLE DB Provider for ODBC and then use OBCD ... So....is there any OLE DB Provider for Lotus Notes??? ...
    (microsoft.public.data.ado)
  • Re: OLE DB Provider for ODBC/Win XP
    ... The Data Sources (ODBC) control panel applet only deals with ODBC data ... You are referring to an OLE DB provider. ... OLE DB has a similar data sources interface. ...
    (microsoft.public.sqlserver.odbc)
  • Samplclnt example in MDAC 2.8: My Story
    ... OLE DB provider/consumer sample that is included in the MDAC 2.8 SDK. ... I started off by attempting to build the sample provider DLL, ... what the consumer client uses to read the rudimentary .csv data file. ... were probably a result of a relatively new compiler working with relatively ...
    (microsoft.public.data.oledb)