RE: Samplclnt example in MDAC 2.8: My Story



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 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 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.

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

  • 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)
  • Re: Samplclnt example in MDAC 2.8: My Story
    ... I was incorrect when I stated that ODBC as a whole is deprecated. ... ODBC provider for OLE DB is deprecated; ... > | compiler errors. ...
    (microsoft.public.data.oledb)
  • Linked server to as400 - for the love of god please help.
    ... i'm trying to setup a linked server between SQL Server and an AS400/DB2/IBM ... OLE DB provider 'MSDASQL' reported an error. ... OLE DB error trace [OLE/DB Provider 'IBMDA400' IColumnsInfo::MapColumnIDs ...
    (microsoft.public.sqlserver.server)
  • Problem with Linked Server from SQL to DB2
    ... I'm trying to setup a linked server from SQL to DB2 UDB. ... Microsoft provided OLE DB driver for DB2 and the IBM DB2 OLE DB ... -- Invalid schema or catalog specified for provider 'IBMDADB2'. ...
    (microsoft.public.data.oledb)
  • RE: Database Lookup Functoid Connection String
    ... A OLE DB provider is a COM component which implement a number of COM ... And connection string is a way to initialize a OLE DB provider. ... accessed by the BizTalk server account, ...
    (microsoft.public.biztalk.general)