> We are having some issues again with our product install (Installsheidl 5.1)
> concerning the msflexgrid.  It seems like every third or fourth test build
> of the install image, we have a major problem with this control.  It just
> will not display and we get some really flaky messages from our app, mBoxes
> dispalying when there is no way they should be in that part of the code.....
> I have traced the problem do to the point where the grid is instaniated,
> blah blah blah.

> Where I think our problem lies is in the OLE/COM 'sub-system'.  We know we
> are dependant on files like comcat.dll, comctl32, olepro, asycflt..... and
> the like.  These problems only seem to occur on base Win95 (the dreaded
> floppy installs), which means we probably upgrade all of these files, or at
> least some of them.

> How do we know exactly what we need to ship with our product?  This is a
> very frustrating thing for us and has almost made us shy s\away from COM
> alltogether.

> Thanks,

> Chris

> Where I think our problem lies is in the OLE/COM 'sub-system'.

> We know we
> are dependant on files like comcat.dll, comctl32, olepro, asycflt..... and
> the like.  These problems only seem to occur on base Win95 (the dreaded
> floppy installs), which means we probably upgrade all of these files, or at
> least some of them.

> How do we know exactly what we need to ship with our product?  This is a
> very frustrating thing for us and has almost made us shy s\away from COM
> alltogether.

> Thanks,

> Chris

>I've similar problems using active-x controls in win95 (first try).

>> Where I think our problem lies is in the OLE/COM 'sub-system'.

>You're right. You can download the dcom98 upgrade from microsoft, which
>can be distributed with your app. This solves lots of problems but not all.
>The best platform using ole/com/dcom is win95 (B or C Version) and installing
>the
>dcom update.