>>So if you're using external PRGs the DoCmd function is not going to open extra doors that were not already open anyways. If someone wants to do something bad they don't need that extra door. Closing down the DoCMD is doing absolutely nothing to security or protection of your code.
>
>And even if all such holes are shut, there's still the possibility that your exe can be run from VFP IDE (via "do the.exe") from inside a .prg where you have an "on key label ctrl+shift+F4 suspend". With 101 keys on the standard keyboard, that would be about 800 lines of "on key label xxx *" just to prevent this kind of trick, executing in the first milliseconds of the start, which I guess nobody has done yet. And then there's the debugger and intellisense in the command window, which make the suspended exe open for surgery.

Would be useless, as there are a couple of similar avenues much harder to stop. The only real protection for a vfp program is to not put it on a user machine - MSTSC allows user input without making things impossible at about 256kb/s. The vfp C compiler proably is the next best thing, making it at least very costly in time spent for the hacker.

Regular vfp Exe are really like the house with open doors Walter desribed


>I had to do this only once, some 15 years ago, but I'd guess this gate is still open.

Given vfp technology it is impossible to close.