What are pitfalls and time elements converting app to web?

[Raccoon]

Hi All;

I have been charged with providing a cost estimate for converting a large vfp6 app to a web enabled app. Naturally, I only have today to provide an answer. (comments reserved ). It would be of great help to me if someone that has done this can give me some pointers on the pitfalls of converting to web based app. I'm aware of the report issues, but am concerned about converting the input screens. How labor intensive is it? Any other areas I should be concerned about? Does the new .NET offer any help? Any and all assistance or comments are appreciated.

Thanks
Mike

 

[jonscott8]

Hi Mike,

If you are only wanting to web-enable your app, that is, provide FTP & HTPP transfers, web links, email, etc, the task is rather simple.

If you are wanting to port your application to a web application, that is, a web interface accessed via a browser, the task could be very time consuming. OTOH, if your app was originally designed as n-tier architecture, the burden would be lightened and the majority of the task would be redeveloping the interface, using ASP for example.

I would highly recommend you visit

http://www.west-wind.com

and read some of the white papers published by Rick Strahl. Rick is one of the leading VFP developers producing web apps.

AFA the .NET issue, I wouldnt even consider this in the discussion. At this point, no one can be certain to where .NET will lead. I've read many articles of developers being displeased with the first .NET beta releases. They have stated that VB.NET is leaps-n-bounds different than VB.

Good luck with the conversion. Jon Hawkins
jonscott8@yahoo.com

The World Is Headed For Mutiny,
When All We Want Is Unity. - Creed