>Hi,
>
>I often had to use some ActiveX component example written for use with VB.
It seems all Active X examples are of the VBA genus - Even third party guys

>It work in VB but don't in VFP5/6.
VBA inside VFP is different than VB. VB, 1 means true, while VFP, .t. means true. etc.

Plus, sometimes, I had to set theAutoYield option in VFP to make it work.
I haven't figured out what Autoyield does - it would be nice if we had a post showing us an autoyield example.

> I often had to trial and test it,wasting lot of time.
At least, with vfp, we can drive the activeX components from the command window. That seems easier than writing complet routines and trying to figure why they are failing.

>
>Why are the Activex incompatible with VFP and when do we need to set the
>AutoYield option.
I would like that answer too. For example, I'm told the CoolBar (though I have some success with it) is not supposed to work with VFP because VFP is not a "native" windows app.
>
>Is there some ActiveX components that are meant for VB and can't be use
>in VFP. I thought they should be compatible.

>
>Please advise me on the problem and solution to this problem. Thank you.
You can drive primary assemble of an active x control from the command window. The code you would normally associate with a method or procedure, may be entered at the command window to test it.