> >
> > If you haven't tested it, then say so. An un-tested solution can still be valid - but it is important to know that it is un-tested
> >
> Ken,
>
> I am really surprised abt expecting complete Tested code. Complicated calls like DLLs i agree but simple syntax errors which gives more pointers on how to acomplish task must usually do. Also no one can write the whole code for someone else. Am i right ?
>
>
> SuhasHegde

I have to agree with you there Suhas. I normally won't post complex code unless I can test it but if it is a simple function or something like that, if I have the time (and if the computer I am at has VFP) I will test it, otherwise, I will simply post it as "Totally untested and off the top of my head."

This is a forum where we share ideas - even untested ideas. I am grateful that someone will post an untested answer to one of my questions (I would like to know that it is untested) but I certainly have no right to demand that it be tested before it is posted.

You are also quite correct - nobody can write code for me. If it is to be my code, then I have to write it. If I use code that someone else has given me, or even if I totally re-write it and just use the idea, I feel it is only appropriate to give credit in my comments, but I am the one responsible for writing my code.

Ken
You shall know the truth - and the truth shall set you free. (John 8:33)