|Think about Loose Coupling|
XML and Databases and Excel, Oh My!by jedikaiti (Hermit)
|on May 12, 2010 at 16:44 UTC||Need Help??|
jedikaiti has asked for the
wisdom of the Perl Monks concerning the following question:
OK, Monks, I'm on the sketching-out-ideas phase of my next project, and I thought I'd see what kind of brilliant insights you can offer.
The mission: I need to pull data out of database and pop it into an Excel spreadsheet for examination/modification by the end user. Then I'll need to get the data back out of the spreadsheet to update (& add new info to) the database. I may also need to compare the changed user data to what's currently in the database, and report back to the user exactly what would be added/changed.
Generally, what I was thinking was this: Get the data (specific details on that will have to wait, there's some debate as to exactly what database we'll be using, so that will be in a holding pattern until that gets sorted out), pop it into XML files, use Excel macro(s) to import the data into an Excel spreadsheet, let the user mess with it, then use Excel macro(s) again to export the data back into XML files, and then use Perl to handle sorting the data and popping it back into the database.
So, I had been thinking that I'd likely use XML::Parser to handle dealing with the XML, but then I hit CPAN and searched for XML modules. That is one long list. Since I have a bit of time to ponder my implementation options while TPTB decide on a database (long story), I thought I'd ask you guys for your input. Is XML::Parser a good choice? Should I be looking at XML::EasySQL instead? Another favorite module I should be looking at? Other ideas out of left field?
Swiss Army Nerd