Printable View
I made a program that runs perfect on Windows 7 32/64-bit but doesn't work on Windows XP. Is there a known issue, maybe in the settings, that I am unaware of? Because I am using a Windows 7 64-bit computer. I'm also making the EXE Setup on Windows 7 64 too. So I'm wondering if there is a compatibility issue there.
vb6 is a 32bit application i do not think that is the problem.
i think it is some api calls in the program that does not work on win xp and works on win7 can you copy all declarations of the API's
With some research I found that the computer I'm compiling on, which is Windows 7 Professional X64 Service Pack 1 has known issues when trying to run the program you compiled on Windows XP. Something referring to a corrupted ADO connection when attempting to make the connection.
so you are using ado? what error do you get on the xp system
it maybe that the references you are using for ado, do not exist in XP, you may need to find the appropriate compatibility libraries
There's a known problem with using ADO and the like when W7 SP1 is used to create the App - it works on W7 but not anything 'lower' I think it's an MDAC problem - search Dilettante's posts, I'm sure he has documented the issue (I would, but I'm just going out)
(Of course, if you're not at SP1 on W7 then I don't think that's going to be the problem.)
EDIT: Ah here it is: http://www.vbforums.com/showthread.p...t=mdac+windows
It's not really an error persay. I don't get a message. Well I didn't at the time because the previous programmer who set it up but "On Error Resume Next," but at the same time that I took all of them out I downloaded a patch from MS fixing the Windows 7 SP1 / XP problem. This was resolved just this morning. Thanks everyone :)
could you post the link for the patch to help others?
As far as I know there has never been a true fix for this in the sense of undoing the damage Win7 SP1 causes. So he probably installed the hack from KB2640696 which you must use by referencing the new version of Msado60.tlb it installs.
This is the same thing we covered a long while back in Win 7 SP1 Breaks ADODB Binary Compatibility which a simple search should have turned up. It's a little shocking that people are still only now stumbling upon the issue.
See Post#6 :)Quote:
Originally Posted by dilettante