I agree with BrowserUk, you are being asked to deal with this totally backwards!
If the volume of submissions is that high then they should contemplate involving IT and have the form submit into a database, then the data can be dealt with there through another interface, or it could be periodically downloaded to the client application.
Typically I have handled this by exporting the data using another small script either into an SQL dump, or a CSV file, zip it up with a password and send it (either by direct download or by email). But have the client contemplate that the better solution - and a less time intensive one for their staff - may well be to approach the problem top down, rather than trying to implement a patchwork solution.
jdtoronto
-
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.
|
