With TAdoQuery (or TQuery), user MUST set some value to get records
from db.
With a where condition, you get only rercords needed.

Think a internet search engine, like Altavista.
You set a value and it find a lot of web page, but NOT
ALL WEB PAGE!

Using query, you can join a lot of db tables to have
a composite result.

If you use client/server db (Oracle, MySql, Db2, Interbase, etc)
you MUST use query insthead Table!

Bye

AS

--
~~~~~~~~~~~~~
?raig ?eynolds
~~~~~~~~~~~~~
Just because this is never going to work is no reason to be negative!

The best way to tell is to hook up an ADO monitor to observe what kind
of SQL queries are issued when you open the table or query.  Several
exchanges can take place while the ADOTable object picks up information
about the field structure of the table being opened.  These exchanges
may or may not happen a second time.

Like I said, the best way to observe it is to "look."  There's a lot of
stuff that a fileserver-based database (e.g. Paradox, dBase) can
discover just by "opening the file and reading the header," which is
very fast.  An SQL-based application can't do that:  it has to
interrogate the server, resulting in several transmission-delays.