aspnet -i wrote: how the Permalink to the answer pointed to the question Just because it only contains #answer8 at the end of URL which no more exist so it landed at question. "When you don't know what you're doing it's best to do it quickly"- SoMad

Totally agree. As it is said: One doesn't offend when they want to do it, only when you let him to do it and Don't argue with an idiot, he will bring you down to his level and beat you because of his bigger experience. I don't know whose qoute's are those, but my father told me them long time ago and I try to have them always present, because they really say the truth. M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.

That was a good point. I agree

Mentions StackOverflow but not CodeProject. Use the best guess

Thanks Chris.. I can see the link and button now.. I dont know what was wrong with it. The buttons were invisible..I cant miss them since I have used them a thousand times till now

I too think its idiotic to have a price barrier to ward off people (If that is their intention). WIth 10k per person they are simply ignoring the frontline\programmers who will be the first to adopt their technology. Wonder what the managers and journalists do during those coding sessions.

I will download other document.

Just my 2cents worth: The comments system allows for any user to see the real history of discussion on a topic. A chat based system would not be tracking that conversation and would render a high number of answers out of context as the comments and discussion of answers provides that extra information. I wasn't, now I am, then I won't be anymore.

Keith Barrow wrote: I was just looking at question where the user wanted a shorter Guid (thus probably negating their usefulness). It doesn't negate it's usefullness; it's merely a random number. Make the number shorter, and you have a higher chance that you'll end up with a duplicate. Make the number longer (two guids concatenated) and the chance for a duplicate gets smaller. It's just a very, very big int. Bastard Programmer from Hell :suss:

Dear Chris Thanks for the info . ( I voted it 4 since it benefitted me.. )

Thank you Chris

What I hate most are those sites that clear every single field you've painfully filled in before and have you start all over again just because you didn't get the captcha right! Try log in at yahoo and you see what I mean (not to mention they even require you to manually type in the @yahoo.com suffix of your ID - how stupid is that?). The stupid thing about captchas is that it doesn't really matter how hard they are: if a bot does have a built in OCR software, it can just try over and over again and eventually it will find a match. It doesn't matter to the bot how hard the captcha is. It's not like it's running out of time somehow. If a bot does not have OCR built in however, even the most simple captcha would do. I highly doubt there is a significant difference between successuful bot registrations on sites with simple or hard captchas! Has anyone ever done a study about their effectiveness?