> -----Original Message-----
> From: Steve Dirickson
>
> > I've grown up in the HP3000 "world" of databases whereby one
> > ALWAYS uses an
> > editor to make a standalone IMAGE schema file [...]
>
> FWIW, I've NEVER used such a sequence. I "ALWAYS" create item, set,
> database, etc. definitions in DICTIONARY; when I have what I want, I
> use DICTDBC and then DBUTIL. At no point do I even see, much less
> manually edit, a schema file.

OK, yeah, you got me on that one -- [gotta remember to NEVER capitalize
words like ALWAYS ;) ]  Unfortunately (for me) I've only worked once in a
shop that even HAD dictionary/3000, [however they were doing "add-on" work
with MCBA source code, so our databases were already designed, so dict/3000
was never used for it's intended purpose.  Personally, though, I did use it,
along with PAL/REX and even Transact, for my own edification.  As I
remember, DICTDBU/DBL was used as a "poor-man's Adager..." ;) ]

In any case, and to further enlighten the crowd, I'd like to point out that
"no HP-3000 will be used (or harmed) in the making of this film" -- what I
mean to say is that I want to use a skill I'm comfortable with (designing
databases using DBSCHEMA syntax) on a Linux system running things like
"mysql", "db2", "postgres", or any similar "sql-based" database/rdbms.  So
while it would be "awfully nice" to use tools such as adager, dbgeneral,
dictionary/3000, PAL, or what have you, unless they are ported to linux, I'm
a bit out of luck ;)

[and I suppose even if they WERE ported to linux, all they would work on is
eloquence databases, which still won't help me and/or my job skills
portfolio outside of our hp3000-based community...]

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