This was kind of my thought... the system has been designed so heavily toward this paradigm it would require a major rework of not only this process but many other processes in the system, and its not my system. I'm working on a deadline and the people I am passing it off to need to be able to maintain it.
I would love to shove this off into a database, cuz I love databases, but unfortunately I don't see this as being the way to go.
The thing I am playing with right now is preprocessing all the holdings files ahead of time and then traversing the shell once, populating all the reports in one big hit... I think it will probably yield the most favorable results without completely disrupting their entire system.
- Ant
- Some of my
best work - (1 2 3)
-
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.
|