Yeah adding the 2 new methods with the extra xVal parameter took care of the problem
but it was tough cause before the other day I had no idea how to go about creating an activex, exposing pucli pems etc so it wasn't a total loss

at first I thought I could just use the get & let propertys for textCellAttribute but I needed to be able to pass in the appropiate row cell etc..

also had some problems with the control not wanting to set the backColor with a variant so I had to create another method that takes long parameter .

Thanks

Greg



>That's too bad it didn't work, Greg.
>
>In the past I've dealt with OLE issues concerning "field collections" in Access that were solved by tagging on a .Value; eg.
>
>oRs.Fields( "CLIENTNAME" ).Value = "..."
>
>The obvious "character index" above would make one think that we weren't really dealing with an array ... which I though might have been your situation.
>
>Out of curiosity I downloaded the TXTextControl ...
>
>Actually, .TableCellAttribute is a GET/PUT method that takes one more parameter in the "PUT" ... though attempting the following didn't work either:
>
>TXTextControl1.TableCellAttribute(tableID, tableRow, tableCol, txAttribute, RGB(255, 0, 0) )
>
>This only returned "too many parameters".
>
>
>>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.