Today, after closer look(!), i found out that non-oledb connectionstrings used with ADO can not be used with ADO.NET
My import application (written in PowerBASIC) used ADO and for only a few parts as alternative ADO.NET's oledb.
I tried the new v2.x's common factory object but the connectionstring is not accepted in several occasions.
Modifying the string with some flawed piece of code is not what i prefer.
The user does not make the choice between ADO and ADO.NET so only the ADO datalink dialog is used.
Anyway, ADO.NET does not (simply) provide a new datalink dialog so letting the end user making the choice is not a real option at the moment.
Someone who knows how to use the older ADO connectionstrings in ADO.NET?
This issue was raised due the fact some newer labtops no longer seem to support ADO.
Updating them with MDAC2.8 is not allowed.
The MDAC installation does not continue for some reason.
If i could update this machine, i would not have a serious use for ADO.NET.
Thanks!
My import application (written in PowerBASIC) used ADO and for only a few parts as alternative ADO.NET's oledb.
I tried the new v2.x's common factory object but the connectionstring is not accepted in several occasions.
Modifying the string with some flawed piece of code is not what i prefer.
The user does not make the choice between ADO and ADO.NET so only the ADO datalink dialog is used.
Anyway, ADO.NET does not (simply) provide a new datalink dialog so letting the end user making the choice is not a real option at the moment.
Someone who knows how to use the older ADO connectionstrings in ADO.NET?
This issue was raised due the fact some newer labtops no longer seem to support ADO.
Updating them with MDAC2.8 is not allowed.
The MDAC installation does not continue for some reason.
If i could update this machine, i would not have a serious use for ADO.NET.
Thanks!

Comment