in reply to Perl and MS Access
...I have no experience with perlIn that case, I'd suggest that you stick with MS Access, which has a reasonable Visual Basic development embedded, and is capable or rendering a UI familiar to Windows users. It also has GOOD debugging tools built-in.
In case I get clobbered for suggesting blasphemy on a perl site, my suggestion is based on relatively minor application scope (single purpose defined by the OP).
"You're only given one little spark of madness. You mustn't lose it." - Robin Williams
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Perl and MS Access
by Anonymous Monk on Jan 15, 2015 at 22:52 UTC | |
by Anonymous Monk on Jan 15, 2015 at 23:01 UTC | |
by RonW (Parson) on Jan 16, 2015 at 01:01 UTC | |
by NetWallah (Canon) on Jan 16, 2015 at 05:46 UTC |