VB Forum / COM / July 2005

I think so : I've made an app under 98SE, and now I mantain it under XP SP2
and it's running fine, on 2000, XP, 98SE and millenium.

Hope this helps

Christian

The only problems I have had in doing this type of thing, is if there were
DCom, or COM+ components.  I've had times where the COM+ Component would
compile fine on the 98 machine, and work within COM+, but when compiled on
an XP/2000 machine, it would no longer work on 98 machines.  I never did
figure out what the cause was though.

Lance

I've been maintaining a VB6 app that was fielded around 2000 and was
originaly compiled with VB SP4 on a Windows 98SE machine.  As my clients
have switched to newer OSs, the VB app keeps running fine.

The app's installation package was created years ago with the DP Wizard.
However, the fielded app is "self-updating" in the sense that it copies
newer .EXEs and .DLLs from the network server to the user's PC before it
starts up.  I have not changed the DP's installation package, but I do
periodicaly distribute updated .EXEs and .DLLs that have been compiled on
the Win 98SE machine.

Now the Windows 98SE machine has become unstable.  I'm setting up a new PC
with Windows XP Pro and I would like to install VB6 (up to SP4) and my
Jet35, Apex, Sheridan, and Crystal components.  Assuming I keep VB and
third-party tools the same as what I have on the Win 98SE machine, will
.EXEs and .DLLs compiled on the new Win XP Pro machine be compatible with
the the ones originally distributed via the DP intsallation package?

Thanks for your help,
Allen Anderson