Gerry,

Unfortunately this did not work, although I tried it right away !

I just spent a grueling 10hrs writing a wrapper ocx control in VB.

Had to expose 122 properites, 44 methods (native to the control), and 60 events !
As well as write 40 new methods to cover the missing attributes !!!

This was the first time I have ever done this so it was quite painful. But at least know I know the ins & outs of creating an ActiveX Control in VB.

Thanks for your input
Greg


>I don't have the TXTextControl, but this type of statement is usually of the form:
>
>TXTextControl1.TableCellAttribute(tableID, tableRow, tableCol, txAttribute).Value = RGB(255, 0, 0)
>
>In this case ".Value" is a typical "default property"; other languages can deal with it, but not VFP.
>
>You may have determine what the "default property" actually is if it's not ".Value".
>
>... Tell Bjorn I said hi ... ;-)
>
>>Hello All,
>>
>>I have an ocx from TXTextControl that is an awesome word processor with great control over most properites and methods BUT it has a few propeties which must be set similar to the following:
>>
>>TXTextControl1.TableCellAttribute(tableID, tableRow, tableCol, txAttribute) = RGB(255, 0, 0)
>>
>>This one property is implemented to control 19 attributes of a table cell
>>
>>The problem is that VFP of course sees an me trying to assign a value to an array element which doesnt exist, thereby triggering a 'Invalid Subscript' error.
>>
>>Can anyone see a way around this ?
>>
>>TIA
>>Greg