From the October 2008 Issue of Prestwood eMag

Interactive Paradox: Using Data: Types of Tables -- Which Type to Use By Mike Prestwood

Posted 16 years ago on 6/12/2008 and updated 9/30/2008 Take Away: Paradox versus dBASE tables. Which to use in Paradox for Windows. KB101185

Paradox is capable of using both local tables (such as Paradox or dBASE) and remote tables (such as Oracle and MS SQL). This means that, as a Paradox user, you can read and write Paradox and dBASE tables and indexes without importing them. This is important. Some developers get confused about this issue and ask how to convert a dBASE table to a Paradox table or vice versa. The answer is, you don't. Paradox is a front end to any type of data that the database engine can access. If you need to copy the data from dBASE to Paradox format, or vice versa, then simply copy the table giving it a new extension (for example .DBF to .DB). The database engine takes care of the details.

In addition to local table structures such as Paradox and dBASE, you can use any of the SQL servers supported by the database engine. This includes InterBase, Oracle, Sybase, MS-SQL, DB/2, and Informix. Also, the database engine is ODBC compliant. This means that you can use almost any ODBC driver to connect to almost anything, including text files, Btrieve databases, Excel spreadsheets, and Access databases.

Here are some general recommendations:

• Power-Users - Use Paradox tables.
   
• dBASE Tables - If you have existing dBASE tables and wish to use Paradox for Windows to manipluate them, I recommend you convert them to Paradox tables. It's slightly easier to use Paradox tables in Paradox then it is to use dBASE tables. Also, help and documentation for Paradox for Windows has more information on using Paradox tables then dBASE tables.
   
• Access MDB Database - Same recommendation as dBASE tables above.
   
• Single User Application - Use Paradox tables.
   
• Multi-User Application - You can safely use Paradox tables but a better choice would be an SQL database such as MS SQL Server 2005. If you wish to use Paradox tables, refer to my Safely Use Paradox Tables article.

Paradox is capable of using both local tables (such as Paradox or dBASE) and remote tables (such as Oracle and MS SQL). This means that, as a Paradox user, you can read and write Paradox and dBASE tables and indexes without importing them. This is important. Some developers get confused about this issue and ask how to convert a dBASE table to a Paradox table or vice versa. The answer is, you don't. Paradox is a front end to any type of data that the database engine can access. If you need to copy the data from dBASE to Paradox format, or vice versa, then simply copy the table giving it a new extension (for example .DBF to .DB). The database engine takes care of the details.

Comments

KB Post Contributed By Mike Prestwood:

Mike Prestwood is a drummer, an author, and creator of the PrestwoodBoards online community. He is the President & CEO of Prestwood IT Solutions. Prestwood IT provides Coding, Website, and Computer Tech services. Mike has authored 6 computer books and over 1,200 articles. As a drummer, he maintains play-drums.com and has authored 3 drum books. If you have a project you wish to discuss with Mike, you can send him a private message through his PrestwoodBoards home page or call him 9AM to 4PM PST at 916-726-5675 x205. Visit Profile