Regardless if it is compiled to IL, they still want to know what was used, all programs, etc.

So tell the truth: you used the Etecnologia product. Having actually checked it out before commenting, I have noted some very interesting options in the menus relating to C#/VB.NET. I would expect that eT will be able to express your eT scripts/forms etc into C# rather than IL or assembly if you want, meaning that you could truthfully offer a C# app maintained using the eT tool. Voila.

You can argue till your blue in the face that it doesn't matter, but it does and mainstream customer want to know what it is when they are paying 7-8 figures for a program and license fees.

Of course I accept that your experience is valid too, which is why eT might consider de-emphasizing VFP. As I keep saying, the principle of a 4GL that allows "do it once" development that can be recompiled repeatedly to use latest technology as it changes and matures, should be exciting even if it uses Lisp or something unfamiliar. The fact that you can start with existing VFP work today is a benefit for people who know VFP but that is not the primary issue IMHO (though I won't hesitate to compile VFP apps today if I can, or at least investigate the possibility before spending $500K to rewrite something from scratch).