On 6/24/05, Cogley, Rick wrote:

Thanks Edgar, and it does indeed clarify.

Since I am on the consulting side, I like your definition no matter the language ;) - the diagram makes it clear.

However, some customers might not accept that, so you might want to add in a calculated / derived field for the elapsed time, should that be what the client insists on. It really depends on how the contract is negotiated in the end. People are picky about things like that, but we would probably show both figures - time on our side, and total elapsed.

Hmmm, I don't quite agree. Depends on the viewpoint I guess... If you send a reply to a customer, and that person is out for a coffee/holidays/whatever and replies again, say, a week later, you want that to count as elapsed time as well? That would make things easier to calculate though.

Will the standalone module be able to export to a csv file from the command line, and if so, can I start testing early? I will feed back to you what I find. It will be interesting to see if everything in utf-8 exports correctly.

Right now it has a web-based CGI frontend, but if you know the variables you want, you can indeed use the 'perl some_script.pl start_date=01-01-2005 end_date=31-1-2005' syntax.

Best Regards, Rick

Kind regards, Edgar 'An approximate answer to the right question is worth a great deal more than a precise answer to the wrong question'