>>>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,
>
>Ok now I know...
>
>There are no problems with the VFP MD5 or the .Net MD5 they both work great.
>
>The real problem lies in how some programer implemented the .Net String to Byte[] conversion. They create a Byte[] twice as big as it should be. Thus nothing matches.
>
>What a waste of time.
>
>Oh well, live and learn.
>
>Thanks for all your help.

Nice you found it.

Programmers !


That is why I converted the string to utf8 first
Watch out for accented chars and the like

I would convert to utf8 on both sides