No not really. I didn't have a solid problem with the RTF itself. But had and replicated and demonstrated with code it simply fails with its own methods if you use some code that'd be fast. If you take longer route that slows down than it's OK (BTW about VFP - some code works after a wait or some delay situation has nothing to do with this. I actually never see VFP code needs wait to work correct if it wasn't me coding wrong). Probably it was for this reason I couldn't get text under mouse with RTF.
Actually ActiveX have problems in common with VFP. ie: Try to place a container in front of an activex like web browser. I couldn't do (and understand they have their own windows). Or try to use an activeX control like RTF in a grid. They behave like images put into grid but unlike solution for images (in FAQ section) I never could solve every row shows the same file problem.
Cetin

>Hi Cetin,
>
>Re: Your rule - use the RTF ActiveX *only* if no other options are left
>
>Hmmm ... I take it that your experiences with the RTF ActiveX have been less than happy? :)
>
>Can you point out some common problems with the RTF ActiveX control so I can determine when it makes sense to use it (not use it)? From time to time I've heard horror stories of trying to distribute this control, but I have never seen anything in 'print' or online to confirm these stories.
>
>Regards,
>Malcolm