irateplatypus

i've recently been coralled into helping the cause of a poor outdated database server. it's running an old version of red-hat, the db software is mysql. the hard drive is failing, removable storage is limited to a busted tape-backup drive (which is to say, no removable storage available). i've been asked to rescue this poor mysql database off this server and place it on the network.

my goal/plan: grab the db off the server remotely (using a winxp workstation) and set up an access db or an excel spreadsheet to display the data. users accessing this data in the future will be unskilled, so i need a no-brainer solution.

i've been trying to use the ODBC hooks to do the import using the "import external data" functions of excel & access (installed myODBC and everything), but can't get my windows box to access the linux machine, even though i can ping and connect by http (it was a crude webserver in a former life).

questions to the TFP database gods:

1. am i going about this the right way, or is there a better solution?

2. if i am taking a good approach, what am i missing as far as getting my MS Office software to link with the MySQL server?

I've exhausted all the relevant google searches, MSDN, and dev.mysql resources i can find... getting a bit frustrated. i'm very used to solving all my problems much quicker than this.

Hope I've provided enough info to spark some thoughts. Post or PM me with any suggestions.

thanks to anyone who gives this a moment's thought.

__________________
If you will not fight when your victory will be sure and not too costly, you may come to the moment when you will have to fight with all the odds against you and only a precarious chance for survival. There may even be a worse case. You may have to fight when there is no hope of victory, because it is better to perish than to live as slaves.

~ Winston Churchill