Connecting with a third party oleDb driver.

  • Thread starter Thread starter Totto
  • Start date Start date
T

Totto

Hi,
I'm trying to use a third party OleDb driver with ADO.net. So far I'v got it
to work with oledbdatareader in a windows application. But trying to do the
same with a asp.net web application gives an error message.
(E_FAIL(0x80004005)Fails when caling ExecuteReader on the command obj..)
There must obviusly be some differance between data objects in windows and
web dev..
Have also tryed the oledbDataAdapter / Dataset, but this gives the same
error in both windows and web dev ( Fails calling Fill on the adapter)..
Is it possible to use some other data source ? Is the old recordset gone
forever ?

Best regards
Totto
 
AFAIK , they're the same object. Probably a permission problem or
something. Also, are you just getting the exception on ExecuteReader and
the Connection is opening correctly?
--
W.G. Ryan MVP Windows - Embedded

Have an opinion on the effectiveness of Microsoft Embedded newsgroups?
Let Microsoft know!
https://www.windowsembeddedeval.com/community/newsgroups
 
Hi, William Ryan
Yes, Connection is opening ok. Its just the ExecuteReader and Fill that
raise the exception.
 
Hi Paul Clement
The database that I'm trying to get data from is an integrated part of a
SCADA system(PVSS from ETM). I don't think it's a file database

Best regard
Totto
 
I have also tried to make a .Net class library to encapsulate the database
activity, where only string variables is passed between the two. But I get
the same error in asp.net wheras in the windows application it's working
flawlessly, go figure

Best regards
Totto
 
¤ I have also tried to make a .Net class library to encapsulate the database
¤ activity, where only string variables is passed between the two. But I get
¤ the same error in asp.net wheras in the windows application it's working
¤ flawlessly, go figure
¤

I'm still fairly certain that it's a file security issue. If not the actual database then possibly a
file library that is used by the database driver. Oracle suffers from a similar issue, where you
have to set the appropriate permissions for the folders that contain the driver libraries.


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