I don't want to ask a bunch of stupid questions that have probably already
been answered ad nauseam.

Can someone link me to some instructional information on getting a Paradox
application to work with an SQL server like MySQL?

Thanks,

Kirk

Check the threads on the pnews server:

nntp://pnews.thedbcommunity.com

....Client_Server group:

pnews.paradox-client_server.

Liz


Kirk_ wrote:

Liz,

I have looked through a lot of those threads and most of it is over my head.
I need a basic starting point. Paradox-->MySQL 101 instruction. :-)

I will post the question there.

Thanks,

Kirk

get myODBC and work as if you were working with paradox tables (slowly).

"Kirk_" <kirk (AT) 1st (DOT) net> wrote

Don't have any links, but some hard learned experience from our lately (and
ongoing) converting of a bunch of tables, forms and reports - from Paradox
to MS SQL.

- To avoid setting up ODBC on each client PC, I have upgraded to Paradox 11,
which can add an alias to a SQL database directly with some additional
arguments.

- tcursors work just as well towards an SQL as towards an Paradox table,
mostly. I have experienced some problems with setrange and setgenfilter as
well as determining how many rows the tcursor contains, so some re-design
has been neccessary. (ForceRefresh may be needed here and there to ensure
working on the most recent data)

- re-designing and using executeSQL with native SQL language has improved
the performance a lot.

- complex data-models on forms where a lot of tables are linked together on
various indexes can slow everything down. I have simplifyed some forms with
much less direct table-linking, using unbound fields instead.

- reports with complex datamodels against SQL is even more hell - absolutely
very slow or hardly working at all. I have had to copy the SQL data to local
Paradox tables to run the reports on these tables.

- Images and formatted memo fields is yet another story of twist and strange
turns, but can be done.

- The upside is no more table repair or lock problems.

Bjorn