The purpose of this thread is to propose a strawman list of conditions that one might consider before posting a Sedna enhancement request. The goal is to keep the list of Sedna improvements focused on what will bring the most value to the community. Simply reposting the existing VFP 10 wishlists will just muddle this process.

Definition of an acid test: An acid test is a list of conditions that must be met in order for a particular request to pass.

Here's my first draft (a strawman if you will) of such a list:

1. If an improvement is available via a 3rd party tool then Reject it

2. If an improvement is a bug with reliable workarounds then Reject it

3. If improvement is a feature that the community can build itself then Reject it

In order to maximize the resources that Microsoft is focusing on Sedna, I think we all need to think in terms of asking for hooks into VFP that will allow the community to implement new features vs. just asking for new features.

Malcolm