Are VB programs distributed from an XP development platform more likely to
encounter DLL problems on a range of target user's systems?



I have been distributing applications developed in VB5 and VB6 for a couple
years now.  Recently I switched my development from a Win'ME  platform to a
Win'XP-Home  platform



I am now occasionally seeing a user install the program and report that
their computer is in some way messed up.  In one case the target system was
Win'98 and the problem was corrected by reverting one of the DLL's
(OLEAUT32.DLL) to it's original state.



The OLEAUT32.DLL problem on Win'98 is well known and documented in many
places on the net.



My questions are -



1.) Are problems like this more common if developing on an XP system? I.E
are XP DLL's and the like worse in terms of backwards compatability? I never
had this happen when distributing from an ME machine.



2.) When distributing the application, would it be wiser to invoke an option
in my installer to not automatically upgrade DLL's, or would that cause more
problems?



3.) Would this be any better/worse if I moved all my applications to VB6?



I am assuming in the above that the DLLs are 'native' to XP and are not
installed on my development system as part of the VB 5/6 installations.



I have the option of going back and doing distribution on an ME systems, so
that only DLL's from the ME system are distributed, but I'd like to avoid
that if possible.



Any suggestions are comments on all this?



Thanks a lot,



Bob Kochem
---
þ RIMEGate(tm)/RGXPost V1.14 at BBSWORLD * Info{at}bbsworld.com

---
 * RIMEGate(tm)V10.2áÿ* RelayNet(tm) NNTP Gateway * MoonDog BBS
 * RgateImp.MoonDog.BBS at 6/1/04 9:57:41 PM