>>>>>>>>>How many psychiatrists does it take to change a light bulb ?
>>>>>>>>>
>>>>>>>>>One, but the light bulb has to want to change.
>>>>>>>>
>>>>>>>>How many feminists does it take to screw in a light bulb?
>>>>>>>>
>>>>>>>>One, and it is NOT FUNNY!
>>>>>>>
>>>>>>>Q: How many statisticians does it take to change a light bulb?
>>>>>>>A: 3, +/- 6.
>>>>>>
>>>>>>Dot netters?
>>>>>>
>>>>>>About thirteen... one to write code, and the others to come up with a proper object model, select the right classes for the job, track the project, write help, draw the icons, write documentation...
>>>>>
>>>>>I think you're going to need a competent management team in on that as well.
>>>>
>>>>And then you need developers to refactor the code and have Agile meetings.
>>>>
>>>>And then they need to move the code to WPF.
>>>>
>>>>And then then need to add WCF.
>>>>
>>>>And then it needs to move to Silverlight.
>>>>
>>>>And then redo it for Azure.
>>>>
>>>>And then the need a new project manager to decide that wasn't what they wanted in the first place.
>>>
>>>Sounds like you're going to need a personnel dept to decide who to let go as well.
>>
>>And then you need to hire a couple of data modelers to make the system ready for the next, much improved data access model that will replace not the latest, but the one before the latest, which is what is used in this particular application. (Rumor has it that it will be a slightly modified but completely renamed VFPOleDB.)
>
>And the app would then automagically be capable of doing its own version control, though it would have to be done not quite from scratch but close, because it would use the new refactored database which uses the latest features of SQL 2023.

Except that, unfortunately, by then SQL Server is disparagingly called Stupid Query Lameness Server, which is considered too Old School and slated for retirement (support ending in 2025) in favor of a new flavor, in-memory cached BinarySearch database (better know as BS, previously known as Rushmore, although MS is betting that none of the old cadre that would remember the Rushmore name would still be around to bring it up.) So, after the SQL Server retirement announcement (during TechEd 2012) the group needs to regroup in order to rearrange its organizational hierarchy with a BS analyst at the top. Oh, wait, there already was a BS analyst at the top? OK, in that case it needs to be a NFBS (New Flavor BS) analyst to replace the OFBS (Old Flavor BS) analyst.

(Does anyone around here work anymore? I sure have to get some billable time in for the day or I'll have hell to pay [with nothing.] See you later... Maybe I should follow Mike's example and try to banish myself from the UT, too. Better I do it than my wife...)