Importing SQL into Paradox 1

[onegurl]

I need help on how to import SQL tables into Paradox9 and maintain a link to the same tables.

Our mainframe data is data-blasted nightly into SQL server. The current corporate method does not use Paradox. I, however, love Paradox (used in another job) - but have never had to link to a SQL table before. The current process here is to import/link SQL data through ACCESS. Data is queried there then exported out into Excel or Word for report formatting. I would love to streamline and automate the processes (many of them) by using Paradox.

Thanks to all for any suggestions.

 

[footpad]

onegurl,

Well, you didn't say which SQL server you're using, but Paradox lets you connect directly to many remote servers using either a SQL Link designed specifically for the server or through an ODBC connection.

In this scenario, Paradox (the software) becomes a front-end for your remote database server. It passes all data operations back to the remote server for handling.

This means that you don't have to import your data in Paradox; you just use it. You can design forms that directly access those tables and honor and integrity constraints built into the metadata, triggers, and stored procedures.

In addition, you can combine, link, fold, spindle, and so on your remote data with any local data (e.g. Paradox and/or dBASE tables).

If you do find you need to covert some remote data to Paradox tables (the file format), this is most easily handled through one of the built in features, either a simple query, the add command, copy, and so on.

This is one of the unsung benefits of Paradox (and the BDE, for that matter): seamless access to remote data and heterogeneous access between data formats.

Hope this helps...

-- Lance