>Many folks have written nice functions which they think are too trivial
>to post in the UT downloads section.
>
>Another reason code is not posted is because we set quite good standards for code in UT and no one wants to face the embarrassment that could occur if their code does does not meet those standards in all respects.
>
>This is a shame, because with .Net posing another challange for us to meet, we should all be helping each other as much as possible.
>
>I propose a free for all dumping ground for code. This area would be completely unatributable and people would use code found there at their own risk.
>
>I call it a code dump instead of a procedure library to make make this distinction clear.
>
>I would love to rummage through this 'code dump'. If I could not understand the code I would not use it. I am confident enough in my own abilities to decide if code could be harmful or not.
>
>Who knows what lies ahead in the future. Lets all help each other and prove that VFP is the best programming environment on the market.

It is perfectly ok, that sometimes, a file uploaded in the Downloads section may contain a requirement for a fix. Thus, in that case, the author is contacted and a fix is then expected.

We can't release a dedicated content for such a need. This would lower the image of the UT and the community here. We have minimum standards that we try to apply on each item and that is part of our image.

If you have some piece of code that you would like to share, don't hesitate to submit it. It'll be our pleasure to make it appears in the proper content. And, as I said, it's perfectly ok that revisions are needed after. We've seen that for several entries so far which have been uploaded such as fixing some piece of code, providing new versions, enhanced with new options and from the feedback requested by the community.