>>> May I just drop in and ask:
>>> how thick these applications are?
>
>The one I've been watching includes the full vfpx library, drag and drop in grids, inlined C++ AES and routines, detailed xml and cursor processing.
>
>- how robust and speedy vs their initial vfp-runtime-based ones?
>
>No visible difference. Potentially the decomposition and other compiler options could cause slow-downs inside tight loops, so you can turn it off in that section of code if you encounter it.
>
>>> how long does it take to adjust and compile?
>
>These days, most glitches are ironed out and many routines compile without issue. If you're using obfuscation you do need to watch out for variable renaming that may break code, but it's easy to prevent this and the compiler watches e.g. for variables that match field names and need to be preserved.
>
>It takes maybe half an hour with one core to compile a chunky app, including the C++ MAKE and compression. One issue to watch for: many virus scanners have a higher level of suspicion for compressed C++ apps compared to pseudo-compiled apps in NET or similar. The solution always is to sign your exes and dlls. These days you can get Comodo signing certificates for maybe $60-70/yr and it's worth it in any case because it adds to professionalism especially during installation or when admin escalation is needed and the dialog identifies the app as being unaltered and from your company rather than unknown.

Thanks for this detailed answer.

By the way, I also tend to believe that getting one's application certified is certainly a good point in to-day's world.

Have a nice week-end!

François