Oddly enough, almost every major Access undertaking I've done myself was easily written in well under 1,000 of Perl. I use considerably less code for the dynamic portions, and all "table" data was stored as flat files-- space efficiency! I needed no more "queries" since a simple sub usually transforms the raw data into analytical data with much more clarity.
The final kick for me is that comparable functionality (especially ODBC access) runs in a fraction of the time. Now, I could be incompetent with Access, but I've used it for about three years to do stuff like this and it never gets any easier. On the other hand, I am frequently able to re-use and adapt my Perl scripts in record time.
I'm not sure an environment is needed, other than emacs for writing the Perl code. *grin* I wrote instructions on installing ActiveState Perl on a Windows environment that were just a few pages that were (imho) fool-proof (standard fool disclaimers apply). And encouraging people to learn Perl itself rather than relying on a system makes the most sense to me. It's not that hard. And it beats having to learn a whole tool and a macro language which is not necessarily portable outside the tool.
So my only heckle would be: teach them Ruby instead! The Windows install for that includes a Net module and Tk support, which means that my three page install manual is one line: the URL for Ruby and the words "run installer". Of course, I'm kidding. Maybe.
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.