Access Violation on some XP machines
Posted: Fri 21 Mar 2014 08:47
Hello.
I stumbled in a problem i could not understand.
I hope you can give me a hint.
After the latest release of my app (using SDAC 6.1.6, as the previous release) on a TMSQuery.Open i see an Access Violation on some Win XP machines.
I could not debug on those machines, but i tried with MadExcept and I foudn the problem was in a TMSConnection.OpenDatasets statement.
i tried to rewrite OpenDatasets as TMSQuery.Open and the AV occurred anyway.
I found a solution: installing SQLServer Native CLient. This solves the problem.
Note: i was not able to find the exact query giving the problem, because on rewriting from opendatasets to .open i coudl not investigate that.
Could you please explain me why?
Facts:
1) on some (not ALL!) WinXp machines there is AV on TMSQuery.Open
2) this started happening in my latest release (where i did not change the code in the method that gives AV or did not changethe sdac version, still 6.1.6)
3) installing SQLServer Native Client makes the AV disappear.
I know XP will be not supported by MS soon, but too many customers has XP, including big hospitals that have not only budget problems (but also sw certifications) problems. So i must support xp for as long as it is possible.
Thanks a lot.
I stumbled in a problem i could not understand.
I hope you can give me a hint.
After the latest release of my app (using SDAC 6.1.6, as the previous release) on a TMSQuery.Open i see an Access Violation on some Win XP machines.
I could not debug on those machines, but i tried with MadExcept and I foudn the problem was in a TMSConnection.OpenDatasets statement.
i tried to rewrite OpenDatasets as TMSQuery.Open and the AV occurred anyway.
I found a solution: installing SQLServer Native CLient. This solves the problem.
Note: i was not able to find the exact query giving the problem, because on rewriting from opendatasets to .open i coudl not investigate that.
Could you please explain me why?
Facts:
1) on some (not ALL!) WinXp machines there is AV on TMSQuery.Open
2) this started happening in my latest release (where i did not change the code in the method that gives AV or did not changethe sdac version, still 6.1.6)
3) installing SQLServer Native Client makes the AV disappear.
I know XP will be not supported by MS soon, but too many customers has XP, including big hospitals that have not only budget problems (but also sw certifications) problems. So i must support xp for as long as it is possible.
Thanks a lot.