>>Actually, Evan's first suggestion still applies. Read articles about creating COM components and FoxISAPI. West Wind has some excellent articles about this. Intranet development is easier than Internet since you don't have to concern yourself with:
>>
>>Browser type or compatibility (Set a standard and upgrade workstations if necessary)
>>Server issues such as loading in house (roll your own) dll's.
>>
>>By controlling these 2 critical components, you can go with fat client solutions using the power of VFP front end capabilities or thin client (ie Browser based) solutions using the power of VFP COM capabilities. Rick has articles on both at the site. If you don't want to roll your own, you can go with West Winds product and load it up on your Intranet Web Server or Active Foxpro Pages loaded on your Intranet Web Server. Intranet apps are a great way to learn since you have fewer headaches. If you want some examples or further clarification, let me know.
>
>To begin, I don't want to roll my own vfp front end program
>(I know it's good but let me the time to learn vfp6). Can I
>use West Winds Product with FrontPage98 and call my vfp application
>directly. Could you give me examples and clarify the steps of
>developpement you suggest.Now I just have one HTML page that
>I modify with FrontPage. For the moment my applications are
>wrote with VFP3, but I have install today vfp6.

If you want plan to go with West Wind, check out Visual WebBuilder (http://www.visual-webbuilder.com/). Its a product co developed by Rick Strahl and Markus Egger. You don't have to use the product, but from my limited exposure to it, it would be preferably to FP98. While I use FP98, I'm not a big fan of it for scripting and/or database development. Visual Interdev has a slightly steeper learning curve but would be another good choice. As for the development steps, that would be too a lengthy reply <g>. Look at the articles on the UT and look at Ricks articles as a starting point. Ricks book is also an excellent source for getting the background you'll need.

Did you put a lot of the logic from your VFP 3.0 app in classes? If so, the transition to web will be easier. Forms aren't going to translate over as easy, but they can serve as a design reference. HTH