Re: Compile Differences, WinXP-Pro and Win2K

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance




"Signet" <22signet7deletethe22@xxxxxxxxxxxxx> wrote in message news:OO0FMe48GHA.4568@xxxxxxxxxxxxxxxxxxxxxxx
>
P.S. A little late to be just now finding out about this problem, don't you think?

Yeah, you're right. ;-) I develop at home, and do some checking of stuff at work, but still missed this. Actually, I saw the problem some time ago, recompiled with different settings (on that machine) and the problem was fixed. But not because of the reason I thought.

Anyhow, turns out the problem is with an OCX that I use, having a different version at home than at work. I can change/update that without a problem, but it's pretty weird, to me, that an app compiled with the old version of the OCX will not run with the new one, and vice versa. That means if I update it, and someone else's app used it (or even a previous app of mine), it will break the other apps.

Would putting the OCX in the app's folder help with this? Will that work with Win95 and Win98 as well? (I'm pretty sure WinXP and Win2K can handle multiple versions of OCXs.)


If the OCX is shared among several apps, then under no circumstances should it be installed in an application's directory. If it's used ONLY by a SINGLE app, then that'd be OK.

It sounds like you didn't maintain binary compatibility with the previous version. Consult VB's Help on this and also see the following:

http://www.vbsight.com/BinaryComp.htm

(courtesy of Ken Halter)

--
Mike
Microsoft MVP Visual Basic


.



Relevant Pages

  • Re: Manifests and VB6
    ... com ocx exe .local. ... I have the same file v. 6.0.96.37 in the app folder ... I don't want to install the OCX in the Windows System32 ...
    (microsoft.public.vb.general.discussion)
  • Re: Ghost breakpoints
    ... and some MFC function was throwing a DEBUGCHK because it couldn't find ... still be able to debug your app but MFC won't choke as your app loads. ... the OCX dll you have is a debug version. ... Steve Kelley ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: VB app nolonger works with XP SP2
    ... I used the MSCOMM32.OCX for the first version of the application (power on ... needed to add volume control. ... did not rely on a ocx. ... The thinking at the time was once the app was ...
    (microsoft.public.dotnet.languages.vb)
  • Re: MSI Installer now pops up when running VB app
    ... or OCX registration. ... that registered the offending DLL or OCX is not longer installed properly ... Where are DLL and OCX registrations saved and how can I remove/change ... Neither the app I'm trying to run or the old app that originally registered ...
    (microsoft.public.vb.controls)
  • Re: VB app nolonger works with XP SP2
    ... ran the .NET Config wizard like you said and it works! ... Run the .NET Config Wizard in control panel. ... The goal was to update the app so it did ... >>volume control and did not rely on a ocx. ...
    (microsoft.public.dotnet.languages.vb)