Re: Converting Microsoft Access to Perl/Tk/DBI

Dump it as tab-delimited text, and you should have no problem. I wouldn't spin your wheels attempting to point Access at MySQL, though, just go ahead and build a TK front end. Building a database from your old data won't take long and you'll be on to the GUI.

Is this local-access only? Personally, I prefer using web front ends wherever possible, especially with Embperl, but that might not be appropriate for you. Worth considering if the opportunity warrants.

Comment on Re: Converting Microsoft Access to Perl/Tk/DBI

Replies are listed 'Best First'.
Re^2: Converting Microsoft Access to Perl/Tk/DBI by bibliophile (Prior) on Jun 15, 2005 at 19:26 UTC
That makes sense. I'm kind of leaning toward the move-the-data-first approach, so I can compare the functionality of the two systems. This particular app is local-access only (although if my planned conversion pans out, there are a couple of other network-aware (ie - multiple clients, one db) apps in my sights...). I wouldn't have the ability to put stuff up on the intranet (that's reserved for "real" developers, sigh). Update:My twitchy fingers had toasted the first paragraph.	[reply]
Re^3: Converting Microsoft Access to Perl/Tk/DBI by samizdat (Vicar) on Jun 15, 2005 at 20:11 UTC
:-) Keep the faith! It's so easy, it's fun. I just made a presentation on my work that puts out graphical web pages from a 1.2GB MySQL database, and I've already had inquiries about it from other divisions of the Labs clear across the base. Pretty stuff sells almost as well as sex! I see I've been downvoted several times for my initial answer to you, and the tool they're describing is probably neat, but very few Access databases I've ever sucked up are complicated enough to require any more juice. Of course, I used to think hand-crafting assembler code was fun... ;-) :D	[reply]