A more complex solution, set up a daemon process on your local host that will communicate with your Access database and pump the results back over the wire to your cgi stuff.
A little more complex, however you can do tricky and cool stuff like convert the output to XML.. You also have the added advantage of being able to modify the backend (perhaps using MySQL or Postgres) without having to modify your web code.
Another advantage is you'll have a common API with which to talk to whatever back you wish! so, you'll be able to scale up your front end, or at least make it a little more extensible.
So this is kinda OT and a little out of scope, but another viewpoint none the less...
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.