Argh! Provider is no longer available! Please help!



I am exceedingly frustrated, maybe because it's Friday afternoon at 4:40 and
I should be home instead of slaving away inside my little cubicle. Sigh.

Anyway, I have an application that needs to expose some data such that other
apps can easily get to it, and the data is tabular, so adding an OLE DB
provider into my app seemed like the way to go.

So I cranked up Visual Studio 6 and selected Insert, New ATL Object, Data
Access, Provider. It created data source, session, and rowset stuff for me,
added the CLSID stuff to my CComModule, the whole 9 yards.

Now, when I load up VB (as a sample consumer) and open the Data View and
right-click on Data Links and select "Add a Data Link", it gives me a list
of "OLE DB Provider(s)" and sure enough, my new provider is right there at
the top. But when I click "Next", it says "Provider is no longer available.
Ensure that the provider is installed properly."

I have various other programs like Access and Excel but I can't get them to
even display the name of my OLE DB Provider.

*** Important: the OLE DB provider classes are in my main application, not a
DLL. I also have in the main application a class with a dual interface, and
I am able to easily access its methods from VB, so I know my COM is
basically functional. I do have to run the app first (I haven't figured out
yet how to tell COM to launch my app if it needs to, that's next).

I have added lots of TRACE to my app so I know that none of the objects that
"Insert New ATL Object" defined are being created, much less having
QueryInterface run on them. There's got to be some basic thing missing so
that VB isn't even trying to invoke my COM objects.

*** Important: Rather than somehow figure out how to call my app with
"/RegServer" on its command line to get it properly installed, I just call
those functions (UpdateRegistryFromResource and RegisterServer) every time
my app runs. It doesn't seem to hurt anything to call them repeatedly ...

Any advice on where to start looking, to figure out what is missing from my
OLE DB provider?

Thanks!
Chris


.



Relevant Pages

  • Re: Word 07 mailmerge source using dbf
    ... Not really interested in a DB Plus app, as just whether any app can call out ... MS no longer supports a dbf datasource. ... Word is trying to connect using the OLE DB provider ...
    (microsoft.public.word.mailmerge.fields)
  • 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: 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)
  • 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)