>>Just to be specific, the Action property in some of the MS controls were generating a 0x800a018a - Unknown OLE status code error. Prior to version 6.0 of the controls, the VFP property sheet was inaccessible (all the properties simply disappeared). While with the 6.0 versions of the control you still have access to the VFP property sheet, clicking on Action brought up the dialog. In VFP 6.0 it's simply marked as "Write-only".
>>
>>It seems as if there're improvements on two fronts: With the controls themselves and with VFP. Hopefully, all of these sort of problems will be a thing of the past.
>
>George -
>
>I was looking at the Report_print (or something like that) class in the Samples.vcx today and whenever I clicked on the common dialog control in the class designer kept getting just that error. I got just the error to which you refer. I had hoped to use this report printing class on one of my forms, but that error spooked me. What does it mean in terms of usability or fixability for VFP 5.0 users?

Hi Sylvia,

I've never had a problem in using a control in an executable that generated this sort of error in development. The only thing that, off the top of my head, I can think of is that you lose the convenience of the property sheet. You can still access the properties programmatically.

It might be best to subclass the control in a container, and use that class rather than keeping individual instances of the control on various forms. I say this, because sometimes when controls are upgraded, attempting to access an existing one becomes an exercist in futility, and cause other problems. By doing this, you simply have to update the original subclassed control and everything derived from that will be updated once you do that.

hth,