Ken writes:
> (6)  With respect to INFORM and BRW, and their "long/short
> term fate" as wondered by Paul:  I don't know about BRW, but
> INFORM was recently enhanced by HP.

BRW appears to have gotten a surprising number of enhancements
over the years, and still seems to have active development going
on.  Anyone know which division owns it these days?  I think it
recently got renamed "Allbase BRW" or something like that, though
it's still the same old program and doesn't require Allbase (it
can natively access Image, MPE, and Allbase files).

It's one of the nicest pieces of software ever to come out of HP
in my opinion.  QueryCalc is probably a more flexible and general
purpose tool, but if you just want to produce a lot of traditional
style "reports", you could do a lot worse than to look into BRW.

One advantage of BRW is that the runtime support is available on
all systems for free, so you only need to buy it for your
development system(s).

> As to Dictionary/3000 not being Y2K compliant:  Yikes !!!....
> Paul is correct.  I just went and looked at the structure of the
> DICT/3000 database (it is standard TurboIMAGE), and sure
> enough:  DATE-CREATE and DATE-CHANGE are pervasive
> in almost all the datasets in the DICT database;  they are both
> YYMMDD X6....  oops....

Does anyone really care?  I assume these fields simply store the
date that a dictionary entry was created/modified?  If so, does
anything ever look at them, and if so, does it sort by them or
perform any other operation which would fail because it's only a
two digit year?  Sounds completely Y2K compliant to me.

G.