Josh:
I tried using the 01/97 version of mscomm32 shipped with vfp5.0a. In addition the the ole errors that appear in many of the properties when it is placed on the form, it crashes vfp (kernel32.dll), when I try to change to rthreshhold to 1 to allow event driven input.

>I think the problem is with VFP, not the controls themselves. VFP recognizes that some properties are read-only at design-time. It doesn't recognize that some properties are completely unavailable at design-time. These are what usually generate the errors. I've found that these controls do work in VFP 5. You just have to ignore the errors. You can still set properties programatically. This does seem to be fixed in VFP 6.0.
>
>The only other control I've had problems with is the MAPI session/message.
>
>>I just started working with mscomm32 and discovered that the version shipped on the Vfp 5.0a CD generates ole errors when placed on a form. In another message, Barbara Palteil suggested using the 8/21/96 version shipped with 5.0 and this works.
>>
>>Does anyone have information on the other ocxs shipped with 5.0a? Is Microsoft aware of the mscomm32 problem?