🚀 go-pugleaf

On Mon, 22 Jun 1998 03:14:31 -0700, "Greg Hill" <ghill@n2.net> wrote:

>Thanks, from both you and Paul, in helping to clarify.
>You mentioned the InterBase that ships with Borland products, yes I do have
>this and played around with it some but still could not get it to accept
>some of the commands that I was issuing.  Maybe I'll jump back into it and
>try some more things.  I got the impression that it was equivalent to the
>local SQL that I'm a custom to in VDB.
>Maybe I did not set it up properly or something.

You have already gotten some really good replies. I would just like to add
some clarification in response to this question.

When you are using local tables (dBASE and Paradox), the BDE parses the SQL
and applies it to the tables. But when you are using some other database
system (InterBase, Oracle, ODBC, and so on), the BDE only acts as an
intermediary. It passes the SQL statement from the application to the
database back-end. In these cases, the BDE does not evaluate the SQL nor
execute it, the database back-end does this. The BDE in turn passes data
(depending on the type of query) and any exceptions from the database
back-end to the application.

Here is an example of the layers involved:

  Application <-> BDE <-> SQL Links driver <-> database system

InterBase has its own system DLLs. The SQL language available is totally
independent from that of the BDE (local SQL). The same applies to other
database types. What SQL syntax you can use will depend on the capabilities
and limitations of the database back-end, and not local SQL.

//////////////////////////////////////////////////////////////////////////
Steve Koterski                      "Knowledge comes, but wisdom lingers."
Technical Publications                -- Alfred, Lord Tennyson (1809-1914)
INPRISE Corporation
http://www.inprise.com/delphi