Hi Frank!

Thanks for your response!

Your suggestion is very much along the lines of what I was thinking I would have to do. I am already doing a STRTRAN(lcWebValue, "'", "''") in order to allow apostrophies to be added to the SQL Server database, and didn't really want to have to call the function twice on each string. I think though (if I read correctly), I can use CHRTRAN() to do replace multiple characters in one shot.

On the other hand, I have been digging a little deeper on the web side. It seems as though the only fields that come across with the mysterious CHR(16) space, are those fields that I used JavaScript error checking on (i.e. date fields, whether or not a required field was left blank, etc.) If any field is even touched by the JavaScript, if the field was blank, it will come into the SQLDB as a CHR(160). Still looking into this one....

Thanks again!

>>And is there anything I can do to force VFP's TRIM functions to trim this ASCII value of a space as well as the standard ASCII val of 32?
>
>You could do something like this:
>

>lcVarName=ALLTRIM(STRTRAN(lcWebValue,CHR(160),CHR(32)))
>

>
>hth,