On 07-08-97  21:11, waiting for 22, Neil Heller said:
 FS> Anyway, I do COBOL mainframe (IBM) programming.
 NH> There are BY FAR more COBOL programs in use today than there are
 NH> programs in all other languages combined.  There are so many more
 NH> people earning a living by writing COBOL programs today than any other
 NH> group of languages that your position is safe ... for now.
Well, I can't imagine by shop ever converting to anything other than
COBOL.  I work for a bank holding company.  They had a hard enough
time converting from the old version of COBOL (OS/VS COBOL) to the
newer version (VS COBOL II).  Although, I suppose I shouldn't say
never.  Back in the early 80's they converted a lot of programs from
RPGII to COBOL.
 
 FS> We use a database system called DL/I (Data Language I).
 NH> That went out of favor in the mid '70s; IBM replaced it with DB2.  The
 NH> same exact affect can be had by combining a modern, relational
 NH> database system (DB2/2, Access, Watcom SQL, etc.) on a microcomputer
 NH> with just about any serious programming language.
Yeah, out of date, I know.  But we still use the old mainframe
operating system VSE, instead of MVS, so what can I say...  I don't
even know of DB2 is available for VSE.
Anyway, so is this the deal...  You write the programs in whatever
language, with embedded SQL calls, right?  Then you run them through
the SQL preprocessor which translates them into language calls.  Then
you compile them in than language and link them, etc.  Is that right?
We have Microsoft Office 97 Professional on our PCs, and Access is
part of it.  Do you build the database itself using the Access
software, say, and then write programs in C (or whatever) with SQL to
access the databases?  I pulled up Access the other day but I couldn't
figure out how to do anything with it.  I suppose if I had read them
manuals or something (as if we had any manuals!)...
        Frank
... I'm sorry, but you've got something I need.
___ Blue Wave/QWK v2.12
--- Shotgun v1.38a
---------------