Yeah, how many tables are these reports generating from? How many different reports? What's the level of number crunching going on? What's the structure of the report? Governmental or private? How exacting are the formating requirements?
That description is exactly nothing. You could NOT build a prototype from that, you don't know the first thing about the data, what's your parameter list gonna look like?
And don't BS us saying you've written a program based on less. That's not possible. While I've worked with some pretty skinny specs in my time I at least knew what kind of data the app was manipulating. This description doesn't give us that.
Yeah, how many tables are these reports generating from? Dude, they're stored procs.
You don't need to know any of that to kick them off.
You simply pass parms to them. He said they were already written, and his ASP tool just had to pass the parms to the procs.
That's all you need to know to build that.
It's *very* simple to do, in fact. In C# *or* Java.