Sletten Kenneth W KPWA <[log in to unmask]> wrote:

...

>SIDEBAR:  Not counting run time for the Adager
>job, the above sequence can be completed in
>about the time it took me to type this.  But
>for cases where someone is making very frequent
>changes to a database, it certainly would still
>be handy to be able to drive all Adager changes
>from a schema file generated from a production
>master DICTIONARY..  Helloooo, Adager...   :-)


Helloooo, Ken...  Loud and clear :-)

I am doing my best to navigate through inevitable
bureaucratic endeavors (not Adager's, mind you,
because we do NOT have a bureaucracy here, but
it has become a sad fact that hp3000-related
strategic matters tend to eat up a lot of time).

Every minute I manage to get, I invest in Adager
programing -- which is the activity that I love
the most.  There are a couple of items ahead of
the schema-interface project that you and other
Adager users have so bravely (and patiently)
championed, and I am making my way through the
priority hierarchy as quickly as I can.

We all want to demonstrate the superiority of
IMAGE's methodology, even if Tom Emerson has
to suffer through 'the Microsoft "access" /
unix "sql" way of doing things' that he so
eloquently mentions.



   _______________
  |               |
  |               |
  |            r  |  Alfredo                     [log in to unmask]
  |          e    |                           http://www.adager.com
  |        g      |  F. Alfredo Rego
  |      a        |  Manager, R & D Labs
  |    d          |  Adager Corporation
  |  A            |  Sun Valley, Idaho 83353-3000            U.S.A.
  |               |
  |_______________|

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *