Thanks Claude.

You are right it is going to keep all parties much happier if we use ASP for our simple web based forms. Your answer finally got me to make up my mind on this. (Our VB guys are happy with the idea as well)

We also have a requirement for more powerful applications that will require extensive validation being built in.

For example an application that allows us to place orders with external contractors for the repair of roads.

These contractors can range from large building corporations to small "one man and his dog" builders.

At present this is managed by a distributed VFP app that passes email attachments back and forth.
This works fairly well but supporting distributed data sets can be a pain, and of course a lot of data is duplicated.


The data involved is complex and quite volumous. I wondering what sort of web technology to use for this type of app as well.



>Using VFP COM mtdlls with ASP is the best of both worlds- you can use the full power of VFP and, on the web, everything appears as just another ASP page. To many marketing departments and VB'rs, the fact that you're using an ASP component means you are already somewhat integrated with what they're used to.
>Check out our resource page at: http://www.activevfp.com
>Also, the best Microsoft explanation, IMO, of VFP's strengths in comparison to their other products can be found at:
>http://msdn.microsoft.com/vfoxpro/prodinfo/qa.asp
>
>>My department is now at a crossroads.
>>
>>All of our really successful systems are written in Foxpro but I am now the only VFP programmer left in our department and am surrounded by VB developers.
>>
>>We are just about to plan for providing web enabled applications and management look as if they may end up giving all this intresting work to the VB developers. This is in spite of them being sympathetic to VFP because it has been such a successful product for them compared to their experience with VB.
>>
>>I need some good sales ammunition to fire in support of VFP in a meeting that is to take place in a few days time.
>>
>>I need to demonstrate why VFP is better at working with the web than the opposition so I need ideas for any sales aids folks can come up with.
>>
>>Ideally I need to see a strong argument that has already been written in favour of VFP on the Web and some working examples showing how easily this can be achieved in VFP.
>>
>>Also I need to know if the crux of the argument I am putting forward is accurate.
>>
>>I will be arguing that if the department is planning to move towards .Net then it should be delivering applications in VFP 7.00 now to take advantage of those portions of .Net that exist in VFP 7.00 (I know VFP is not going to be in the CLR but I dont think that is an issue)
>>
>>I am very hazy on this whole area. Am I right in thinking that VFP 7.00 has good support for SOAP built in or is this only possible by using a third party product like WestWind SOAP manager.
>>
>>Where does XML figure in all this, can I use that as a selling point. The only advantage I have is that the VB guys seem to be as ignorant as me in these areas.
>>
>>I think this thread could become an important one for all of us because these are the sort of arguments that VFP developers are going to have to win somehow the world over.
>>
>>All help most gratefully received.