A bit of history. When I worked on the Fox team in the late 90s, I worked on a project converting a VFP bug tracking app called RAID to make available as a web app sample in VS97 using ADO and RDO, with JavaScript and DHTML using IE4. I liked the .eval() method in JavaScript, and got Calvin Hsia to prototype it in VFP instead of having to hack via string to file then COMPILE file.prg, and he created it, then I created a spec document, and it got approved for the product (I think VFP 7.0).

I used my RunCode program in _webbrowser4 instead of ExecScript because it uses my {{}} recurrsive evaluation code, from GenScrnX. So you can run this code:

*foo.prg

x = "VFP {{4+5}}.0"

Then the code that runs above is x = "VFP 9.0", and recursion is supported in {{expression}}

>Yes, _webbrowser4 definitely makes life easier. I ran across others that use the vfps:// "protocol" even though they aren't using the FFC class, so it's something of a standard. Of course, I had to override the RunCode() method to use ExecScript(), it's still using RunCode.prg! :)
>
>>This seems like the best workaround. The web browser control focus issues have always bugged me, and I even tried to get the IE team to change or allow customization of the behavior as a hosted ActiveX control, but it's been like this for years (since IE4 I think). Glad you're having fun with my code in _webbrowser4, and my undocumented VFPS (VFP Script) method. :)
>>