Guenter,
AVFP encourages putting the app logic in a VFP component(vfp mtdll). The presentation interface is totally separate. I'll go out on a limb here, but, I think AFP emphasizes mixing VFP code with the presentation layer, in this case, html - just like classic ASP...
>Claude,
>sounds good. Will check over the holidays what serves my purpose best.
>
>I´ve not yet decided how far I want to take this from the original VFP app. (Actually it was strictly FP coupla months ago. <g>)
>
>If I look at the development it seems that we´re moving from proc centered (FP) to form centered (VFP3,..) to database centered (VFP8, SQL-Server), where the logic is in the db. I can´t afford (time-wise) a paradigm shift every other year.
>
>The easiest option might be to keep the VFP front end and just serve the data over the Net, so I´m contemplating CursorAdapter.
>
>OTOH, if I can keep the app logic in FP code - embedded in a Web form - I could push farthest. Do you think this sounds like AFP -- or AVFP???
>
>Thanks for your time and merry Christmas!
>G
>
>>>ActiveVFP(AVFP) is a framework for developing VFP mtdlls that are called from ASP or ASP.NET(the only one I know of that works w/.NET). It includes a VFP web application generator called WebAppBuilder that sets everything up - you just add your app logic. It has an interactive debugger(thanks to Maurice de Beijer) and generates extremely fast VFP web apps. Probably the best thing is that it's free and includes all of the source...<<