I agree with you totally and thank you for taking the time to mention all of this. Realistically, I do not know right now if there is a clear business case for the rewrite unless the rewrite is outsourced - which is a definite possibility if they are hardset on getting it done. That incurs additional costs (huge ones). All those decisions will be made when the documentation which contains the options and pros/cons of each is completed. We are looking at all possibilities. That option presents another set of problems/issues as well.


>Tracy,
>
>I forgot to add that we concluded that if we stopped on the current product and committed to doing a total rewrite it would take us 24-30 months to beta, which meant unhappy clients who pay TS&M ( no releases for 3 years basically ).
>
>Interesting what Roy says. That is our situation here. I am on the team that was the original team for the last 10 years and against a total rewrite so myself and the other 2 original developers were dropped from the "new" team ( 4 fledgling coders ) people and told to keep the curernt product going. We are moving on along our own path that I drew for you yesterday and the other team is attempting a total rewrite. The funny thing is they are not asking the knowledge base ( us ) how the app is suppose to work of for any input and they are not able to plan for the updates we perform on the existing product, so we are prediciting the same thing Roy saw.
>
>Rewrites are neat if you go loads of cash and time, but in the real workd they are impracticable when you have an existing revenue making product and limited resources. I know a story about a daddy bull and a baby bull standing on a hill looking down at some cows, but this is not the forum for that story. It teaches walking is better than running sometimes.