Re: SQL vs. 4GL

Path: emory!swrinde!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!rutgers!ub!dsinc!das13!dave From: dave@das13.snide.com (Dave Snyder) Newsgroups: comp.databases.informix Keywords: SQL, 4GL, standards Message-ID: <1619@das13.snide.com> Date: 7 Feb 92 11:48:52 GMT References: <wemhoff.697427191@judy.cs.iastate.edu> Organization: Snide Inc. - Folcroft, PA In article <wemhoff.697427191@judy.cs.iastate.edu>, wemhoff@cs.iastate.edu (Becky Wemhoff) writes: > I'm working in a new Informix shop, and there's a minor debate going > on here about when to use SQL code only and when to use 4GL code. We > all agree that a simple one-time-only report will be SQL'ed. However, > our current 4GL guru would like everything else written in 4GL. The > SQL guru thinks that the code would be simpler and easier to maintain > if we could write most of our applications in SQL. I remember reading a story about Domino's Pizza. They had a similar dilema. When they finally finished their project of ~300 programs only 6 were written in Informix-4GL... the rest were either Perform screens or Ace reports. The shop I work at is just the opposite... of ~580 programs about 12 are written with Perform/Ace the rest are Informix-4GL. Personnally, although 4GL will give you "cleaner" looking screens/reports, you can't beat the ease of development with Perform/Ace. I'd suggest doing as much as you can with Perform/Ace and doing the heavy-duty things with 4GL. DAS -- David A. Snyder @ Snide Inc. - Folcroft, PA Current Release is db4glgen-3.4 UUCP: ..!uunet!das13!dave INTERNET: Dave.Snyder@snide.com