Steve,

Well done!

Having worked as a developer, I've been on both sides of this.

While working at a bank, I was asked to do pretty much the same thing, fed the same lines almost verbatim.

Now, this was a web application, and there was a page counter which logged hits from each page to an SQL database. The enhancements they asked for required the creation of an additional 5 asp pages. The implementation was what they asked for; and it did exactly what they wanted.

I spent about 2 weeks creating the new features and guess what? They used 'em about 2-3 times a month, and it didn't justify the time spent on it.

On the other hand, there were some other features that did add alot of value, one 'bulk-change' utility I wrote saved the company countless man hours.

The point of this is - I think too much 'feature creation' without enough forethough can cause developers to get jaded or disheartened when they put alot of effort into something that doesn't get used.

Just my 02c...

Mark