Very informative, very helpful, very well spoken. You stated:

Actually, "...does essentially the same thing as the one in C..." begs the question "Then why did you do it?" ("Because it was old" doesn't fly - it was working. Maybe it's a reinvented wheel to them as well as you?) Can you make it better in visible, obvious and valuable ways prior to displaying it? It'd be better if they and the users, are happy to get it.

I should have been more clear. I said that it essentially does the same thing. There was a small database(about 15mb) with information that needed updating, and it needed to be accessed faster. There are several things that were written to make new needed functions more automated, and access to several new systems, much easier, in addition to similar functions that the C version provided. The C version could not have accomplished this, with out a complete re-write/major upgrade, and I really didn't feel like picking through someone else's code, we all know how that works out.
Not meaning to go into detail, but I wanted to clear that up.

-- Yes, I am a criminal. My crime is that of defyance.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.