For those new to message boards please try to follow a few simple rules when posting your question.
Choose the correct forum for your message. Posting a VB.NET question in the C++ forum will end in tears.
Be specific! Don't ask "can someone send me the code to create an application that does 'X'. Pinpoint exactly what it is you need help with.
Keep the subject line brief, but descriptive. eg "File Serialization problem"
Keep the question as brief as possible. If you have to include code, include the smallest snippet of code you can.
Be careful when including code that you haven't made a typo. Typing mistakes can become the focal point instead of the actual question you asked.
Do not remove or empty a message if others have replied. Keep the thread intact and available for others to search and read. If your problem was answered then edit your message and add "[Solved]" to the subject line of the original post, and cast an approval vote to the one or several answers that really helped you.
If you are posting source code with your question, place it inside <pre></pre> tags. We advise you also check the "Encode "<" (and other HTML) characters when pasting" checkbox before pasting anything inside the PRE block, and make sure "Use HTML in this post" check box is checked.
Be courteous and DON'T SHOUT. Everyone here helps because they enjoy helping others, not because it's their job.
Please do not post links to your question into an unrelated forum such as the lounge. It will be deleted. Likewise, do not post the same question in more than one forum.
Do not be abusive, offensive, inappropriate or harass anyone on the boards. Doing so will get you kicked off and banned. Play nice.
If you have a school or university assignment, assume that your teacher or lecturer is also reading these forums.
No advertising or soliciting.
We reserve the right to move your posts to a more appropriate forum or to delete anything deemed inappropriate or illegal.
Maybe this is where an idea comes in that I read about some time ago. It was talking about localization, specifically for number-based data such as postal/zip codes and telephone numbers. It went on to say that basically, you don't store the formatted data. You store the numbers only. No spaces, no hyphens, etc. That makes it simple to localize the data when presenting it on the user's screen, and I'm sure it makes a difference in validation as well.
djj55: Nice but may have a permission problem
Pete O'Hanlon: He has my permission to run it.
That's quite right. But in the UK plenty of organisations seem to get confused about it. Some insist that you don't include the space, and some insist you do. So I guess plenty of developers have not read the article you refer to.
In such a thing there are two levels of validation. One is for the format and the other is for the value...
Like in email...the email email@example.com is perfectly valid in manner of format, but hard to believe anyone will answer you from it...
The same for US zip codes, it can be easily validated for format using regex, as it or a 5 digit number or a 5 digit + hyphen + 4 digits number. However not all validly formatted zip codes are real zip codes...
If you read carefully you may came to a - fairly complicated - regex that validate not only format, but also value (I have done that for Israeli phone numbers, so it is possible as long you have some rules) - http://en.wikipedia.org/wiki/ZIP_code#Structure_and_allocation[^]
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
תפסיק לספר לה' כמה הצרות שלך גדולות, תספר לצרות שלך כמה ה' גדול!
Since the encryption key will be needed by both client and server, how will be able to share the key with both without exposing it to the hacker community at large? The answer is that you cannot, especially since the client will likely have the decryption key (or same key if you're using symmetric encryption) exposed and vulnerable.
"The oxen are slow, but the earth is patient."