RE: Solution WAS config.list ???

[Tony Tofts]

> Tony my system is too littered with many copies of the ocx.
> Why not one copy in windows system that gets updated and
> remove the seperate copies from each vb app ?

Hi Steve,

This is a 2 edged sword really.

I originally decided to include the ocx with each vb6 app for simplicity,
and because it meant that non-win98 users wouldn't have to update all their
applications, just because of a minor update to the ocx.

Given the problem Frank has had, and the fact that (other than any possible
minor bug fixes) the xpl.ocx is now in it's final version your suggestion
is
probably the best action to take.

The following is probably the route to take?

Add a separate page on the website for the xpl.ocx which contains the ocx
for those who know how to manually update the ocx, and an install package
for those who prefer the windows route, along with instructions.

Add a note to the top of each vb6 page pointing out that the ocx is
required.

Remove ocx from vb6 zip's

If anyone feels there is a valid reason to keep the ocx in the individual
zip files, please let your reasons be known today ;-)

Many thanks
Tony