>>Are you kidding? How can you hide it with those bunch of exe, dlls, dbc, fpw, and many more obvious fox file extensions? Doing this is hypocrisy in nature.
>
>Its not tough, how would you know a VFP DLL from a VB DLL just looking at it. The FPW could be built into the app. Most other Fox Files could be flat out lies.

Bunch of little stuff that would be a real pain to hide- like changing the source application's name in the print queue for any document that was printed from VFP- and changing the name of the application when certain fatal errors occur ("Visual Foxpro caused a fatal blah blah..."). ALso, hope the app makes no use of WAIT WINDOWs, and never tries to quit without CLEARing EVENTS ("Cannot quit Visual Foxpro"). VFP leaves a pretty clear trail...