Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!apple!agate!shelby!portia.stanford.edu!chesky From: chesky@portia.Stanford.EDU (Snehylata Gupta) Newsgroups: comp.databases Subject: Re: Ingres buyout! Message-ID: <1990Sep29.163415.3069@portia.Stanford.EDU> Date: 29 Sep 90 16:34:15 GMT References: <1990Sep27.145216.12068@morrow.stanford.edu> Distribution: usa Organization: AIR, Stanford University Lines: 40 In article <1990Sep27.145216.12068@morrow.stanford.edu> AR.BXA@forsythe.stanford.edu (Bob Anderson) writes: > Stuff deleted >My knowledge of ASK is now 5 years old, and is quite likely >not up-to-date, but... > >MY recollection is that the ORIGINAL ASK product (MANMAN) >and it's follow on products (OMAR , AP, GL >FA, SERVICEMAN etc) we're all particular to a manufacturing >application, were written (in FORTRAN , for HP's >proprietary IMAGE DBMS. I know they operated in that mode >exclusively for quite a few years, because i was S/M on an >old HP 3000/70 that was bought exactly because it was the >ONLY platform for ASK. Altho i was more into systems at the > > stuff deleted >bob anderson >stanford > Your recollections are correct. Currently I am working for one of ASK's biggest clients. Our platform is VAX VMS the system is till wriiten if FORTRAN. However ASK is rewriting their system in INGRES (ABF/4GL ? ). The current system is robust so I doubt whether existing clients will jump to the new platform. My guess is a lot of current ASK clients will wait for a while after the ASK product is released to evaluate the performance of the INGRES based product before committing. to the new system. (Please note this is not my employers opinion just a practical evaluation. It does not reflect on ASK's or INGRES Corpn's abilities.) INGRES has it's share of pitfalls as I am sure the developers at ASK have been discovering. Sanjay (Not my usual disclaimer : The opinions above are solely my own and are not those of Stanford University or my employer.)