Replies

Let's look at exactly what he said:

It was a custom reporting application. The user enters parameters into a Web Form, then ASP.NET fires off a series of SQL Server stored procedures. A background process runs MS Access to generate Word .RTF report files, and ASP.NET provides the user with links to the newly created files. Not a huge and complex enterprise application by any means, but there were plenty of tricks to work around.

From what I see they wrote the front end and the stored procedures, which probably means they also owned the DB tables. 2 tiers as you put it. As I've said OVER AND OVER AND OVER AND OVER AND MAYBE SOMEDAY YOU'LL ACTUALLY LISTEN BUT I DOUBT IT, because we know ABSOLUTELY NOTHING about the actual data we know ABSOLUTELY NOTHING about the scope of the project. And any software professional that actually knows which orifice to point at the screen knows there isn't enough info here to estimate with much less actually start writing code.

Maybe simple stuff, maybe not. It would take a week to do this if the data were something simple like checking account info. You try writing this stuff to pull TWC or TRS data (Texas school stuff, all the info's on the web but if you read it you will bleed from the eyes, real nasty stuff) and come back and tell me it'll take a week, go ahead try it.
The size and scope of the data and complexity of the reports is a major factor. And if you don't know that then it's clear all this "experience" you've outlined on countless threads is a lie.

Read Jeeves' Post 33:

The ASP (VBScript - yuk!) database code was all rewritten in VB.NET - it really wasn't ported so much as used as a model for the ASP.NET version. The Transact-SQL stored procedures required no changes, nor did the existing MS Access reports.

He was very specific. You're incorrect, and must have missed some of the details.

The stored procs and existing reports were not part of the '.NET' app, and didn't require any changes. We're only talking about the form.

You're not even a developer, if I remember, but a tester, yes?

This is plenty of info to give an accurate estimate of time. And a day or two would be *plenty*.