Hi Martín,

>
>Sedna is not a specific extension for a certain type of application, but a collection of different extensions or improvements.
>
>- The upgraded SQL migration wizard is just a (much) better migration tool. It is not something you will use every day, but it could help migrating data from DBFs to SQL Server if you need it.
>

This is certainly useful. But I thought that the upsize SQL tool is part of the VFP9 SP2. Maybe I am mistaken.

The rest of the features you describe seem to be impressive. And for those of us who are truly experts in VFP and .NET (and I am not even remotely close to them) the features could be academically interesting. But I simply don't have time to learn something for the sake of learning. Unless I see a practical feature(s) that I can add to my application, learning Sedna will take a low priority. I am not knocking Sedna, of course.

Thank you very much for your input.

>- The MY namespace is a collection of libraries that can look simmilar to the Fox Foundation Classes in the sense they provide you with shortcuts to specific functionality already available via Win32 API, WSH, .NET, etc. But the most interesting stuff is the way Doug managed to expose that, providing something like namespaces in .NET for VFP. It is extensible and hierarchical, but it load on demand instead of actually building a huge object.
>
>- The NET4COM library is a COM wrapper to serveral .NET libraries, allowing you to use some .NET functionality. Last time I checked, most things could be done using the Win 32 API, but I guess they implemented more. Again, something useful is been able to check how they did it.
>
>
>I'm surely forgetting something, but beside that, the most important thing is that you get the full source code for Sedna as a learning tool, and you can change and redistribute it as you please.
>
>
>Hope this helps,