5c9b757f   
   From: jeffshoaf@alltel.net   
      
   Well, since nobody (including me) has really answered your question...   
      
   You could always set up Paradox to access your Access database via ODBC,   
     do your query in QBE, then use Paradox's QBE-to-SQL tool to convert   
   the QBE to SQL, then copy and paste the resulting SQL query into Access.   
      
   In exchange, here's a question for you: why do you think Access has a   
   faster engine? Which version of Access - they've changed the engine   
   several times over the years... And if you develop in one version of   
   Access, there's little chance that it'll run on a "pre-loaded"   
   installation of Access if that installation is a different version....   
      
   Regardless, if you get Paradox Runtime, you can build an install package   
   that will load the Paradox runtime and your application at the same   
   time. That gets around your concern that Access is pre-loaded on more   
   PCs than Paradox.   
      
   All of that being said, it's well worth the effort to learn SQL. Both   
   Access and Paradox have limited futures, and almost any database you   
   might move to will use SQL - it's the database querying "standard."   
   Here's a good book to get started:   
   http://www.bookpool.com/sm/0596526849   
      
      
   Jan wrote:   
   > I'm using Paradox 8. MS Access has a faster engine and installed on   
   > more computers by default, so ideally I'd like to use Access - but the   
   > QBE interface of Paradox 8 is so easy to use while Access query design   
   > often require SQL programming for something as simple as counting   
   > unique vs non-unique occurances in a column.   
   >   
   > Any suggestions? Any tool for using Paradox-like QBE query interface   
   > in Access?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)