>>Many thanks for this Kenneth but my problem appear to be more basic.
>>I have a screen with 3 controls on it
>> Ok button
>> Ole Control - WangImage.EditCtrl.1
>> Ole Control - WangImage.AdminCtrl.1
>>
>>On an XP machine this appear to crash as the AdminCtrl loads - if I remove just that control then the app does not crash.
>>
>>Any thoughts?
>
>Hi Caroline,
>
>I did just the same - 3 controls, with no properties set - and my form loads OK.
>
>I am using a pretty old verion of the controls - 4.0.0.1063. Any chance it may be an issue with version compatibility?
>
>Are the versions of all the OCXs consistent?
>
>Do you get the same behavior if added programmatically? as in ...
>
>

>THISFORM.AddObject('WangAdmin','OLEControl','WangImage.AdminCtrl.1')
>THISFORM.AddObject('WangEdit','OLEControl','WangImage.EditCtrl.1')
>

>
>or
>
>

>LOCAL loObj1, loObj2
>loObj2 = CREATEOBJECT('WangImage.AdminCtrl.1')
>loObj1 = CREATEOBJECT('WangImage.EditCtrl.1')
>

>
>Maybe assigning one button each to instantiate them may shed some light? You can ascertain that it's the Admin control when you click on the button to instantiate it.
>
>Or perhaps it is just a case of the VTable Binding thing ?
>
>Other than that I am really at a lost as to what else could be it !@#$
>
>Working with ActiveX controls is definitely not as straight forward as dropping a TextBox in on your form. Recently I had to find a workaround for something that just couldn't work in the TreeView control. I probably spent a good deal of time on it which would have been for more productive work. The same went with the WangImage.ScanCtrl.1. It crashed and crashed until I got it tweaked right. What a world!

Thanks again for the input I will have a play with your button instantiation idea.