Ole Db

[bvivekb4u]

We are developing OLE DB data provider for our database engine. It is having some problems while using it through .NET and MS SQL Server Integration Services.

I am suspecting that our provider is not behaving as it is expected by OLE DB Core Components and Services. I would like to know about different OLE DB core components and flow of operations when these components are used by consumers and providers. I could not find any documentation refernces about OLE DB core services. MSDN just mentions THERE EXITS somethinng called OLE DB Core Components.

This is deep dark area for us. Unless I know expected behavior I can not correct provider's behavior :)

Thanks,
Vivek.

PS: I am sorry if this not the place for this post. But I could not find any proper forum this query. If there is any such forum, please point me there.

[debasisdas]

You might find something useful here .

[bvivekb4u]

You might find something useful here .

I have been googling for a long time. I have already gone through almost every bit of the specifications related to ole db services. The link which you have mentioned has no details of how it works. If you go through that then you will reallize that it has nothing more than just 'what is a specific service'. And that is the problem :(

Anyways I could narrow down a little more on this problem. I will describe that in another reply.

Thanks,
Vivek.

[bvivekb4u]

I did some tracing. My observations are-

Connection string is built as

"Provider=MYOLE DB;Password=pas sword;Data Source=myserver ;User
ID=admin;Initia l Catalog=SYSTEM; Window
Handle=984398;P rompt=CompleteR equired"

The last property-

'Prompt=Complet eRequired'

causes this issue.

I tried this with simple c# test program to connect. If we pass the whole
connection string as above it gives the error--

"Format of the initialization string does not conform to the OLE DB
specification."

It works fine if we pass connection string removing last property, i.e.

"Provider=MYOLE DB;Password=pas sword;Data Source=myserver ;User
ID=admin;Initia l Catalog=SYSTEM; Window Handle=984398"

So the problem is that the connection string built contains
'Prompt=Complet eRequired' at the end. Our provider returns DBPROMPT_NOPROM PT
for DBPROP_INIT_PRO MPT property. Still why the connection is built as
'Prompt=Complet eRequired'?

Is it because of something missing with a set related properties?