if you consider thata complete description remind me never to test your code. All I see is the languages and tools, nothing on the size of the DB or front end, nothing on the kind of data. There's a big difference between a reporting app that pulls data out of something like a home CD inventory and one that pulls out of a fully flushed HR/ payroll system. I know governmental payroll reports that will take you a week just to figure out what the hell data they're looking for. To even pretend you can give development estimates off of what scant data Jeeves put out is patently rediculous.
All I see is the languages and tools, nothing on the size of the DB or front end, nothing on the kind of data. He said it was a web form that allowed the user to enter parms, and then passed the parms on to the SQLServer stored procs. He said the app then returned links to the user.
This is a very complete description, and yes, I could build a prototype from that info.
I've had less to go on at least once!!! And that app turned out to be a smash success.