Your description seems to go completely against the "best practice" of separating the "data storage/management" from the "business logic" and the UI.
It is not at all clear from your code where you are obtaining and storing the data, and what is being passed to what.
That said, If I were to design this app/DB, I would display a form asking for quantities ordered, store that quantity , and date requested into a database table , then use a separate program to email or print the invoice (This program would read from the Database - no structure should get passed, perhaps some simple scalars for customer number, date, or possibly an invoice number (for possible re-printing,e-mail). Such a request could/should also be made via a database record, so that a record of request completion can be kept.
"As you get older three things happen. The first is your memory goes, and I can't remember the other two... "
- Sir Norman Wisdom
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.