jan,
While you will need ODBC, you don't need to export your Paradox data to files that are later imported into MySQL. Instead, you can use Paradox itself to transfer (or directly edit) your remote MySQL tables directly, as if they were Paradox tables themselves.
This requires a bit of set-up however:
1. Verify the version of your MySQL server. It needs to be relatively recent. If it's not, you may need to pester your administrator to bring things up-to-date.
2. Install the MyODBC driver on your Windows machine. It's free and can be found on mysql.com. Be sure to reboot afterward.
3. Using the ODBC Administrator in Control Panel, create a USER DSN pointing to the MySQL database on your server. Work with your administrator to collect the appropriate values for configuring this driver, as some servers require different log-ins for web access vs. data entry/administrative access to the database.
4. Use either the BDE Administrator or Paradox itself to create an aliases based on the USER DSN you created. Test it by trying to connect.
Once you've done all this and gotten it working, then Paradox lets you open tables on your database server just as easily as you can open local tables. You can then use Copy, Add, Subratract, queries, and even ObjectPAL to manage that data. (It's actually one of the best features of Paradox, thru heterogeneous access to multiple, disparate data sources.)
Note: You may be tempted to include the database username and password in either your ODBC DSN or your BDE alias. Do NOT do this unless you can guarantee you will be the only person using that computer. These are stored as plaintext in your Registry and easily accessible by anyone with the slaightest amount of knowledge. It may not seem like a risk, however, it may be instructive to use RegEdit to search for Keys containing "password", "pass", "pw" and other varations on the phrase. I know I was rather startled with the results.
Hope this helps...
-- Lance