From: bjo-sag@online.no   
      
   "Kirk_"  wrote in message   
   news:46337d36$1@pnews.thedbcommunity.com...   
   >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?   
      
   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   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)