>We are stuggling with the distribution requirements for Cal Widgets 32bit OCX.
> In our experimentation we removed OLE2.DLL, COMPOBJ.DLL, STORAGE.DLL,
>OLE2DISP.DLL, etc. (actually renamed them ".old") on a Win95 machine.  We
>confirmed that all instances of these DLLs were not on the system (using the
>Find feature in Win95).  We then ran our VB4 32bit app using the 32bit OCX and
>everything ran fine.  We asked Sheridan about this and they insisted the 32bit
>OCX still requires all those OLE2 16bit DLLs.  We found that the OCX will not
>load if OLE32.DLL and OLEAUT32.DLL are not present... but does not seem to
>give a{*filter*} about OLE2.DLL, etc.  Has this been your experience?  Could
>Sheridan be wrong about its' own product???  We thought that perhaps the DLLs
>were already loaded... so we re-ran the test... with the same results.  
>Further, you cannot rename a DLL that is "in use"... and we were able to
>rename all the 16bit OLE2 DLLs while our 32bit app was running... we are
>confused!  It would be great if someone could confirm our findings with their
>own test to make sure we are not missing something obvious.

>I think your confusion is in assuming that all the OLE DLLs will be
>opened just because your app is running.  OLE uses it's own DLL's on
>demand ( like an OLE server).  The only way you could find out for
>sure would be to exercise all ( and I mean ALL) the functions of your
>ocx application and monitor whether or not each of these
>"questionable" DLLs are ever opened or not.  I think that you will
>find that Sheridon is not wrong about their requirements,they are
>echoing the specifications that M$ has laid out about what minimum
>files are required.  My bet is that your app will eventually crash
>somewhere if you leave out the DLLs.
>--
>J. Boyd Nolan, PE

>Voice:(405) 739-1916    FAX:(405) 739-1095
>Boeing Aerospace Operations