Ken,

Les Pinter said, in a recent FoxTalk column, that it took him 2 years to develop his framework. Based on the length of time it took Visual Promatrix and Visual FoxExpress to reach market, I think that's a good estimate. Your boss, like most people in most situations, most likely will underestimate the complexity of everyone else's job. He really ought to have a copy of Rapid Development (Taming Wild Software Schedules) by Steve Mcconnell (Microsoft Press, 1996) on his desk, and read a couple pages before every meeting he has with you.

Hank

>After all the threads on here about which Framework to use and their pros & cons, has anyone actually developed their own framework? If so, how complicated was your design, and what kind of a timeframe did you look at?
>
>Reason: My company has a 'Standard App' that they have developed. The functional design was well thought out, but it was developed before I started. The programmers that did the development had no previous exposure to OOP/OOD and did the best they could with what they had. Problems have come up around the issue of reusability and extendability. I have recommended changing their approach and using a framework to create their apps from instead. The current design does not allow for reuse into apps that are not a 'Clone'. I have looked into using a Framework, such as CodeBook for Mere Mortals, but this is not really an option at this point. With the combination of the learning curve and the time to recreate our current functionality into this framework would be too time consuming. Due to the specifications in place, our best option is to create a framework specific to our needs.
>
>Objective: I have to make a presentation to my boss regarding timeframes, budgets, etc. next week. {Another rush, rush project. Aren't they all? :-) } I have some general ideas regarding time to develop, but would like to get some other input from colleagues to broaden my perspective.
>
>Any input will be greatly appreciated...
>
>TIA