>>I'm trying to make my opinion on the good use of the Autoyield property. I've come to the following conclusion: generally you should leave it to its default value (.T.). But if you have use an ActiveX control on a given form, you should set _VFP.Autoyield = .F. in its init() and reset it to .T. in its Destroy() . Do you agree with this simplistic approach?
>>
>>Althought it should be much easier to set it to .F. at the top of the application, I've experienced that it generates at least refreshing problems.
>
>When using Mabry and Catalyst FTP OCXs, I had to set it to .F. to be able to have the Progress() event fired. Otherwise, I would not have been able to show a progress bar.

Michel,

Same for Sheridan calendar widgets. With Autoyield set to .F., the refresh is *much* cleaner, and VFP does not miss events. Otherwise I had to put a WAIT .10 or something like that to be reasonabliy sure my AfterDelete, or AfterSave or other code would fire.

José