🚀 go-pugleaf

> Does that mean a 'broader' SQL command set which can be coded right into a
> VDB app?  I guess this is where some of my confusion lies.

Sure.  In 5.x local SQL was week, so I used SLQExec() a fair amount to get
things done on my particular back end, which is an AS/400.  When working at
home or on my laptop, I kept a model of key tables in a local Interbase
database and could mimic most everything I needed from my production
environment simply by changing a single global property (the name of the
database to open).  I used the so-called "Data pump" to do a fair amount of
that at one time, and it worked pretty well, creating Interbase tables from
AS/400 data sources.  As long as they were flat tables there were no
problems.  Multi-member tables were another story, but they're problematic for
ODBC anyway, so I already had logical files (akin to SQL views) set up on the
AS/400 for those situations.

7.x has addressed some of the limitations of 5.6's local SQL, but there are
still things you might want to do on a back end that are beyond it's scope
(for me that's frequently subselects and calls).   I don't really need the
capability as much these days, but I keep local Interbase loaded just in case.
:)

>> Kens marketing-minded reply <G>
> -------------------------
> He may have provided me with more 'marketing' information than I ever
> received from Borland on this.  <bg>

A trait endemic to the Borlander species, no doubt.  And no doubt the Inpriser
one shows the same tendencies.  Anyway, Ken's back on TeamB now, so we expect
his level of marketing schlock to decrease as his level of jovial inanity
increases. :)

kgc