Tom,

I don't like cold weather so I think I don't regret being here in FL, warm and happy. <g>

Well, maybe this is another "frying pan", but the actual system is solid and has structure and arquitecture too. And if I succeed and make happy 400+ clients, the rewards will be great, in all fronts. That's the difference.

As always your input is great, but I think something got messed up when you sent it, can you please resend it complete? I don't want to miss a word!

Max

>
>Now you have left one "frying pan" for another! :) This sounds a lot like your last application in some ways.
>
>The opportunity to create a desktop/web application from an existing one is a huge task. Do not stay up all night to “finish the code”! :)
>
>You know the way I am – I like details in outline form. You have given a general overview so I will respond to those.
>
>

>1.  Turn off computer and define system requirements.
>     A.  Always a good idea and you have the source code.
>     B.  Define a detailed plan and timeline with management’s approval.
>
>2. Approaches:
>     A.  Use a commercial application framework for the desktop version
>          1.  ComCodeBook is interesting and multi tier
>	     A.  Contact YAG for details about his web site.
>	     B.  I can send you the manual to read until his site is back up.
>	     C.  Business logic will be a COM object and shared with all
>	     versions.
>          2.  Consider a stub exe with individual apps.
>	     A.  Divide each major module into a separate app project.
>	     B.  Deliver a new module when it is completed.
>	     C.  Your menu will make the call to the new module.
>
>
>	     B.  West Wind/Voodoo for the Web version
>
>I could get into detail later – at this point we are exchanging concepts.  By the way I have converted several apps from DOS FoxBase, and Windows 2.6a, into VFP applications.  Several approaches were taken.
>1.  Use prg’s and spr’s and pull them into VFP.
>     A.  Ugly!  We had to make constant changes to the application.  First you had to go back to the original tool, make the change, pull it into VFP and compile.
>2.  Complete re-write.
>     A.  Several approaches were taken.  There are many considerations.  What hardware do your clients have?  Management will be the first and final guide.
>

>
>If you would like the ComCodebook manual let me know. The framework is free and is not presently available as YAG is in the process of getting the site back up. It is good food for thought. Also contact Rick Strahl to see what he thinks about the web app concept using West Wind and Voodoo.
>
>Planning and understanding the application requirements is key to any projects success. With ten man years invested in the application I am concerned about maintenance and new features of the present application. Will you be doing this also? Or are you there for a rewrite of the present application. I have been involved with two projects that had ten man years invested. How soon does management expect to see “results”.
>
>By the way - I would stay away from ASP! Just ask me why! :)
>
>Ciao.
>
>Tom
>