Do you really not know what SednaX is (or actually, was)? It's a community effort to enhance VFP. It's now been renamed VFPX. It's at http://www.codeplex.com/Wiki/View.aspx?ProjectName=VFPX

The VFP team has never had responsibility to create or maintain ActiveX controls that ship with VFP.



>A link to Steve's Blog:
>http:www.//sellenoff.blogspot.com/
>
>Begins second entry down.
>
>I was searching for some info on VCX and OCX and I found "Steve".
>
>He talks about Sedna X - he - as many of us - wonders why MS's VFP team has not assured that OCX controls have kept pace with VFP releases.
>
>It almost as if MS is telling us not to use active X - essentially - they are telling us to write FoxBase or dBase TXT applications.
>
>But he did mention Sedna 10 and the fact that his OCX ComCtrl VCX is being looked at as something to be included in Sedna 10.
>
>Why has Microsoft forced us to jump through hoops just to get our VFP apps with OCX controls up and running on an MS OS?
>
>Why is it so difficult for MS to do this?
>
>And, what is SednaX?