After re-reading the original post, I think I may have inferred more than I should have.

Specifcally,

• I don't know that the code is all in one file, the OP just said "a program", which might or might not mean that


• I don't know that the code is uncommented. The OP said there was little or no doc, which may or may not mean few or no comments.


• I don't know that the globals, stated as beinng form "g_xxx", are really 3 letter names preceded by "g_" - the names my well be longer and more descriptive than I thought.


• I don't know what's in this code - 8000 lines is a LOT of perl code.

So if I take the optimistic view of each of these questions, for all I know, this may not be such bad code. The lack of doc, lack of -w and lack of strict still make me suspicious, but maybe this code can be used and adapted.

I still think you have a very steep learning curve to climb, in that you have to learn a tremendous amount in a very short timeframe to be able to either modify the existing code with good understanding, or to write original code, however simplified, to make the new reports.

In addtion to perl, SQL, HTML and (possibly) javascript, you'll also need to understand webserver function, and a litle Unix experience at least in order to debug, so I am still not convinced that either of these is possible, on your own, by October 31st, even devoting full time to it.

--Bob Niederman, http://bob-n.com

All code given here is UNTESTED unless otherwise stated.