Re: Messages to List Being Truncated

Usually it should be \\\ to get a \ ... now lets take a look at your regexp .... /^[a-zA-Z0-9\(\)]{1}[ a-zA-Z0-9\(\)_\,\.\-\'\"]{1,999}$/ ^[a-zA-Z0-9()] should work, as ( and ) only needs to be escaped when not within an []-block (cannot recall the name right now) [- a-zA-Z0-9(),.'\"\\\_]{1,999}$ should be correct here, i am not sure about the >>.<< and >>,<<. >>'\"<< should be replaced by >>\'"<< if you use single quotes to build the pattern. Full regexp would be: #^[a-zA-Z0-9()][- a-zA-Z0-9(),.'\"\\\_]{1,999}$# or even easier: #^[a-z0-9()][- a-z0-9(),.'\"\\\_]{1,999}$#i I replaced the delimiter / with # as you don't use it within the regexp and using / makes escaping the >>/<< even worse ( guess it's 7 / then ) Hope this helps you :-) -- red Pablo Gosse wrote:

<snip>

the first one was truncated but the second one was complete. Btw thx Chris for opening up yet another thread that could have been avoided if your client was configured correctly.

</snip> This is strange. At any rate, I've put the message in an html page on our server. http://www.unbc.ca/regexp.html If anyone could take a look and give me a hint as to what the problem might be I would greatly appreciate it. Cheers and TIA. Pablo