>>Thanks Gregory. I will go back and check the UTF encoding.
>
>(1) Do not forget to dispose() of the MD5CryptoServiceProvider() object
>
>(2) In case you do not trust vfpencryption71.fll you can use windows api : http://www.atoutfox.com/articles.asp?ACTION=FCONSULTER&ID=0000000627
>
>Success,

Thanks.

I've tried 3 different VFP MD5 tools and all give me the same result. I trust the result in VFP. I'm still wondering what happens after I send the text over a web service that the .Net MD5 does not match. I have got to be missing something obvious.