>Hello everyone,
>
>What would help me and my VFP associates, is some clarification on what the Sedna suggestion should/could be, for example: When creating views, or SQL-UPDATEs can we request enhancement to have the “SQL Statement Too Long error (8192 statement limit)” be extended etc., or would this not fit into the Sedna VFP9 add-on. If anyone could please advice, Thank you.
From the Roadmap (
http://msdn.microsoft.com/vfoxpro/Roadmap/default.aspx ):
The primary goal of Sedna is to expand on the ability of Visual FoxPro-based solutions to better integrate with other Microsoft products and technologies.
Features in Sedna will target Visual FoxPro interoperability with application components created by using Visual Studio 2005, the .NET Framework 2.0, and SQL Server 2005.So, the keywoard is "interoperability". I understand that, while any kind of suggestions are going to be welcome/read/considered (?), suggestions related to interoperability will have the most likelyhood to actually make it into the final product.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
