QBE

besides what Jeff said, why would you ask an Access question here, instead
of an Access forum?

--
Steven Green - Myrtle Beach, South Carolina USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards

"Jan" wrote in message

> 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?
 >> Stay informed about: QBE 

"Jan" wrote in message

> I'm using Paradox 8. MS Access has a faster engine

Jan,

The MS Access engine is actually slower than the BDE. In fact, my tests have
found that used correctly the BDE flies and that includes SQL databases.

Anyway, hopefully I have mis-read between the lines, because I get the
sinking feeling you could be migrating from Paradox to MS Access ? Please
tell me this is not the case, because it really is a waste of energy in the
wrong direction. I suggest you look at Firebird and MySQL for starters.

Leslie.
 >> Stay informed about: QBE 

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?
 >> Stay informed about: QBE