>i have a need to generate the checksum value that is from sys(2007) from c# to coordinate a C# application with a vfp application - so it HAS to be sys(2007) compatible values.
>
>i was able to find a fox pro version of code that simulates sys(2007) http://fox.wikis.com/wc.dll?Wiki~CRC16 but converting it to c# is a little tricky. maybe there's some vfp to c# conversion website engine out there like there is for vb.net to c# or vice versa. I know vfp and c# don't necessarily transfer over but this is just using bit operations, data conversion, and some functions that seem to be making the process of conversion a little tricky.

I was looking at the bigger picture. Maybe you have a contract, and part of that is to be compatible with VFP SYS(2007), so that's what you need to do.

OTOH if it's ultimately being used for security/cryptography such that the owner of the product can claim it's "secure", that isn't so. If that's the scenario there are some things you might want to consider:

- If there's a security breach involving a user of the C# product, the owner of the software may say "Ed Johnson wrote that security function, I expected it to be secure, it's clearly his fault"

- Pointing out the lack of security in CRC16/32 gets you ahead of the curve. You'd have to decide if that means "hero" or "whistleblower" :) That could result in more work for you.