ADO broken in W7 SP1
-
I just hit this problem today when recompiling an ADO-enabled project in VS2005 after installing Windows 7 SP1. After an hour of frantic Googling I found this[^] and this[^] and managed to get it to compile again, with testing on XP machines to follow soon. As MS is apparently no longer recommending we use ADO, what should I be changing my C++ programs to use to talk to SQL Server?
-
I just hit this problem today when recompiling an ADO-enabled project in VS2005 after installing Windows 7 SP1. After an hour of frantic Googling I found this[^] and this[^] and managed to get it to compile again, with testing on XP machines to follow soon. As MS is apparently no longer recommending we use ADO, what should I be changing my C++ programs to use to talk to SQL Server?
viaducting wrote:
As MS is apparently no longer recommending we use ADO
I did not read that in the links you provided. Can you point it out to me? It'd be a small game-changer if all older software would suddenly stop to work :)
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
-
viaducting wrote:
As MS is apparently no longer recommending we use ADO
I did not read that in the links you provided. Can you point it out to me? It'd be a small game-changer if all older software would suddenly stop to work :)
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
Please note that VB6 and .NET ADO interop are not supported anymore. This forum post does not imply any future support of these out-of-support technologies.
and
we drastically underestimated the number of customers who were recompiling ADO applications on Windows 7 SP1. Even worse, when I say drastically, I really mean DRASTICALLY."
suggest to me that MS aren't expecting people to still be actively developing ADO-based projects.
-
Please note that VB6 and .NET ADO interop are not supported anymore. This forum post does not imply any future support of these out-of-support technologies.
and
we drastically underestimated the number of customers who were recompiling ADO applications on Windows 7 SP1. Even worse, when I say drastically, I really mean DRASTICALLY."
suggest to me that MS aren't expecting people to still be actively developing ADO-based projects.
viaducting wrote:
Please note that VB6 and .NET ADO interop are not supported anymore
That's saying something about VB6 and ADO interop. Not a statement on the future of ADO.
viaducting wrote:
suggest to me that MS aren't expecting people to still be actively developing ADO-based projects.
Second statement merely explains how a specific bug surprised the team.
viaducting wrote:
suggest to me that MS aren't expecting people to still be actively developing ADO-based projects.
VB6 is deprecated, and yes, I imagine that they extend that to the combination of ADO and VB6. There is no official statement that ADO is being phased out.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]