Resolving DAO and other dll conflicts between XP and Windows 7
I have a VB6 program that uses an MS Access database and runs happlily on XP. When I package it for install and try to install it on a Windows 7 machine, I get "version conflict" mesages for several dlls, notably MSVCRT, msjter40 (and the others associated with the Jet engine and installed on $WinSysPathSysFile) and dao360 (installed on $MSDAOPath). I seem to remember there is a way of having multiple DLLs versions to get round this but haven't been able to find much on how to do this. Can anyone help, or point me at an article on resolving this? I don't want to disturb any of the newer versions - but if I choose to keep them, I can read from the database but not write to it.
Dave Baldwin
This page http://msdn.microsoft.com/en-us/library/ms810810.aspx says that DAO is not supported after Windows XP. And there is no 64-bit version of it.
ASKER
Thanks Dave, in that case I should be able to run it in XP compatibility mode, or am I being overly hopeful? If I alter the code to use ADO instead, do I still need XP compatibility mode, please?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Very persuasive - decided to use XPMode as a stopgap while getting rid of Access. Beeen looking for an excuse for a long time, truth be told. XPMode did everything it promised to - impressive result. Thanks for the pointer to what I should be doing!
You're welcome, glad to help.