By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,846 Members | 1,514 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,846 IT Pros & Developers. It's quick & easy.

converting exclusive DAO connection object to an ADO.Net connection object

P: n/a
Hi guys,

I have a vb application that uses Jet.Oledb with DAO 3.51 over an MS
Access database. New enhancements being done to this application is
done in C#.Net. The vb application thus hosts the .net
components.Normally the vb portion uses the dao connection, and the
..net portion of the application uses ado.net oledb connections. Now the
problem is that there are certain features for which the database needs
to be opened in an exclusive mode. This means that once the vb
application opens the database in exclusive mode, the same connection
object should be used by the .net portion of the application to access
the database. This poses a constraint on the usage of ADO.Net in the
..net portion of the application.

Is there any way to handle this situation? Can we use the handle of hte
DAO connection object and pass it to the ADO.net oledb connection
object.

Thanks in advance.
Mnm.

Sep 12 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Mnm,

No, you can not. You will have to import the DAO data access libraries
into your code (through COM interop) and access the data through there.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com
<ma**********@gmail.comwrote in message
news:11**********************@e63g2000cwd.googlegr oups.com...
Hi guys,

I have a vb application that uses Jet.Oledb with DAO 3.51 over an MS
Access database. New enhancements being done to this application is
done in C#.Net. The vb application thus hosts the .net
components.Normally the vb portion uses the dao connection, and the
.net portion of the application uses ado.net oledb connections. Now the
problem is that there are certain features for which the database needs
to be opened in an exclusive mode. This means that once the vb
application opens the database in exclusive mode, the same connection
object should be used by the .net portion of the application to access
the database. This poses a constraint on the usage of ADO.Net in the
.net portion of the application.

Is there any way to handle this situation? Can we use the handle of hte
DAO connection object and pass it to the ADO.net oledb connection
object.

Thanks in advance.
Mnm.

Sep 12 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.