Not to turn this into PdoxMonks; but, I would like to offer some points to ponder based on the responses so far:

• You're right; there aren't any modules for Paradox. Part of this is due to the fact that *Borland* still owns the rights to BDE and refuses to extend it. They also are playing games with Corel with the source (e.g. "How much can we milk them for this?") There *may* be a DBD::BDE::Paradox driver submitted to CPAN in the next 12-18 months, but it ain't gonna happen soon. If ever. (Read this as saying I could really use some help on this.)

• As far as why anyone would choose Paradox, well, I won't go there. Suffice to say that there are very technical and valid reasons for choosing it over the other big name *local* database format in town. Interested? /msg me privately with your email; we'll take it offline.

• Yohimbe has identified your two major strategies: either export your tables (or query results) to CSV and then import those using BDB::CSV *or* create a custom upload file using ObjectPAL's textStream methods, an approach I happen to prefer. For example, I have a Paradox system that runs a periodic process to publish Paradox data into static HTML pages *and* auto-uploads those to a web server. It ain't rocket science. HTML is just tagged text.

• I suggest that you consider the corel.wpoffice.paradox-web newsgroup currently hosted on cnews.corel.ca. While you'll confuse the heck out of them (save one) when you post Perl related questions, you will run into a group of earnest and well-meaning folks trying to do the best they can with the tools available. They've done good work and if you harsh them (he said, extending adamantine claws), I will come down on you, tho' you may not realize it.

  They will tell you about CWS and how it can be used to provided direct access to Paradox using the tools Corel has provided. Listen carefully, smile nicely, and read between the HTTP lines. CWS is lame, but an experienced Apache tech should be able to figure out what makes the Windows-based BDE work under WINE (or, for the OS challenged, Windows itself)....and that is the key. You may be able to use ODBC, but the best *ahem* access to Paradox tables comes through BDE.

• kschwab provices a decent enough link, but it's not *enough*. Again, if you have troubles with Corel's support, please /msg me. I canna' promise miracles, but I know an answer or three.

• Sierra is mostly right. You *should* have Paradox 9.0, but perhaps not for obvious reasons. Paradox 9 and/or WPO2K/Pro ships with Merant's (TCFKA Intersolv) ODBC driver for Paradox. This is ***far*** superior to the one provided with MSO (*spit*, *ptui*). Merant has elected to charge through the nose for this; Corel provides it free with the Developer's Edition or the Pro version of the Suite. You do the math.

• If you insist on doing the MS ODBC drivers, well, heaven help you. At the very least, make sure you've got MDAC 2.6 installed and BDE 5.11. Stuck? Let me know privately.

• Paradox isn't dead and resistance is not futile.

This is a product I have more than a passing familiarity with. 'Nuff said.