Derek,

Actually, your question is a good one. I don't think I would resort to trying to modify the EXE. A really robust error handling scheme can prevent VFP from displaying any information identifying itself and you can of course change the icon on you forms and the _screen so that your own icon appears.

A few years ago I bought a Genealogy application (TMG) from http://www.whollygenes.com/. This application was written in VFP and although I bought it because of my family research I must confess that I also bought it because I knew that it was written in VFP. That application was so tight and error resistant that it was a true joy to use! If you didn't know that it was written in VFP you would never have guessed it. So, it IS possible to mostly hide the fact that an application is written in VFP. However, your users will always be able to look at the runtime files, the types of files generated by your app, and the files used to store data and be able to deduce that your app is written in VFP.

The best chance of really hiding the fact that your app is written in VFP is if eTechnologia ever finishes their vfp.net compiler. Given that, your app will really NOT be written in VFP and you won’t have to try to hide it. Unfortunately though, it is not certain at the moment that they will ever finish. I still have hope because it is a truly awesome tool!

I hope this helps.

Steve