Make data available to Excel, Access, ...

[Achim Domma]

Hi,

sorry for the cross post, but don't know which of both groups would be the
best one.

I have implemented a .Net DataReader and DataAdapter for our custom data and
it works fine so far. Now I want to make the data available to Excel,
Access, ... One solution would be to develop a OLEDB Provider in C++ via ATL
Templates. But I wonder if there is a simpler way!? Can I develop a OLEDB
Provider in C#? Or is there a mapping between OLEDB and .Net Datasources?

regards,
Achim

 

[William Ryan eMVP]

Unless the sizes of the tables are really large, Web Services would be a
nice way to do this.

--

W.G. Ryan, eMVP

http://forums.devbuzz.com/
http://www.knowdotnet.com/williamryan.html
http://www.msmvps.com/WilliamRyan/

 

[Paul Clement]

¤ Hi,
¤
¤ sorry for the cross post, but don't know which of both groups would be the
¤ best one.
¤
¤ I have implemented a .Net DataReader and DataAdapter for our custom data and
¤ it works fine so far. Now I want to make the data available to Excel,
¤ Access, ... One solution would be to develop a OLEDB Provider in C++ via ATL
¤ Templates. But I wonder if there is a simpler way!? Can I develop a OLEDB
¤ Provider in C#? Or is there a mapping between OLEDB and .Net Datasources?

Not exactly sure what you're asking. Are you saying to you want to build a .NET DataReader and
DataAdapter for Excel and Access?

OLEDB is based upon COM and a .NET wrapper has already been provided as I'm sure you are aware.
Communicating with Access or Excel typically requires interfacing with the Jet database engine and
Excel ISAM driver respectively (although you can use XML Reference Schemas for Excel).


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)

 

[Chris Darnell]

Achim,
We really need a little bit more information. Are you using the
DataReadar and DataAdapter to pull information from a database? If so, then
why don't you use the built-in database connectivity of Access and Excel to
get the data?

It would seem to me that the only reason you'd want to go from a
datasource -> .NET -> Access/Excel would be if the data was not physically
accessible by Access/Excel (i.e. stored on a web server far, far away) and,
like William Ryan pointed out, you'd probably use ASP.NET to present a Web
Service.