Hi Gary,
Technically, the VFP mtdll approach works great with VFP6 SP5 and above. True, the ExecScript native VFP function (for scripting) is available only in VFP 7, but, I usually keep all the code in the mtdll. IMO, if someone is serious about VFP web apps, they should probably have a copy of VFP6 SP5 or higher anyway(benefits of speed, stability, etc.). The real benefit of going this route is that you don't have to purchase the 3rd party tool along with worrying about licenses, etc.
V2 is happening as I get free time (which is limited right now :(...
>Hi Claude:
>
>Thanks for the additional info. FWIW, I appreciate all you have said. I just feel that overall, the MTDLL approach is a better one with VFP7+ (I use VFP v7 exclusively). For a more "traditional" Fox shop, the scripting engine label for WebConnect/FoxWeb/AFP is an appropriate representation, to differentiate between the products/methodologies and their approaches to the same problems.
>
>Any news on ActiveVFP V2 yet? I am looking forward to news of its release.
>
>Best