Michael Hodge wrote:
> Thanks, Matt - or, at least, thanks for being honest!
>
> Some time ago, I gave my wife an old laptop, loaded with 98. As she and
> computers are like oil and water, I think that I can safely experiment on
> her machine. We'll see how things go!
>
> Alternatively, I presume that I have to tell those who want my program that
>; it is for XP (or Vista) only?
>
> Michael
>
>
Then your answer to compatibility problems is at hand. Load up a
copy of VB6 on the lappie. Copy your source project onto the lappie and
compile it there! By compiling on the oldest possible version of
windows you will avoid most of the pitfalls of backward compatibility
with controls and DLL sets. You will have far less problems with DLL
hell and "unexpected error quiting" dialogs. And your XP/Vista users
will never know anything about it as your installer will not install
over newer versions of files.
You will still need to install win98 specific requirements on win98
machines. But with a decent installer (not the package and deployment
wizard) you can actually include the requirements on the CD and have the
installer install the things based upon the versions on windows. I
used to use inno setup for installs, but I understand that there are
better products out there. Perhaps others could recommend something
better to you.
The final 'trap' with installers is allowing them to install part of a
package. The package and deployment wizard is notorious for installing
bits of the Jet engine, but not all. Your should consider installing
MDAC and Jet as downloaded from the MS site rather that the few Jet DLLs
etc the wizard actually identifies as being needed. Further if you are
using reports created with Crystal be warned that they are almost always
installed without 1/2 the support DLLs actually needed for full
functionality. (the inf file produced by Seagate is woefully
inadequate. Something that seagate appeared unable or unwilling to
correct.)
Matt
.
