I know those tools, none of them are 100%, but the point is that when the client knows which development platform has been used they have a headstart in terms of having it decompiled.Derek, this one is essentially 100%:
http://www.baiyujia.com/f_download.asp(click the link beside VFP compiler)
It obfuscates heavily and converts your app into a small VFP wrapper exe with a proper (C++, not VFP) dll doing most of the work. No longer is it possible to Hook or abuse strtofile to seize your sourcecode. The interesting thing about this method is that theoretically it could be used to create a NET dll with the VFP part as an unmanaged extension.
To prevent the VFP errors on C000005 you would need to edit the runtimes. AFAICS there is no obligation to report that your app or crashes are attributable to VFP. However, these sorts of crashes should be rare in VFP9 and if you're obfuscating and protecting, your competitors will have a heck of a time if they need to rely on a C000005 to get a heads-up on your development tool. ;-)
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
