Path: utzoo!attcan!uunet!seas.gwu.edu!fc185120 From: fc185120@seas.gwu.edu (Lish Ethan A.) Newsgroups: comp.databases Subject: Re: PROGRESS HLC question Summary: HLC versus HLI on PROGRESS(tm) Keywords: fork PROGRESS HLC Message-ID: <2273@sparko.gwu.edu> Date: 26 Oct 90 15:44:46 GMT References: <1376@nixsin.UUCP> Organization: The George Washington University, Washington D.C. Lines: 43 In article <1376@nixsin.UUCP>, koerberm@nixsin.UUCP (Mathias Koerber) writes: > Hi, I got a question concerning PROGRESS (V5.2I) Host language call: > > I'm planning to add some network support (send/rcv data via sockets) to > my progres, so that I can have a procedure running as a kind of information > server in the background without having to run progress on the client machines > itself. > Greetings - I am confused! Let's start with the basics: PROGRESS(tm) currently has two products that interface to 3gls (Host Languages). The first product Host Language Call (HLC) is used if the user is logically in the database/PROGRESS(tm) process and the developer choose to "CALL" a 3gl routine. The second product Host Language Interface (HLI) { AKA Embedded SQL } is used if the user is *NOT* logically in a PROGRESS(tm) process. This allows the developer to "SELECT" data from a PROGRESS(tm) Database. In your situtation where you have a PROGRESS(tm) RDBMS Server running on the Network Server and a User running on a Network Client, You should use HLI to "REQUEST" the data from the Server. I hope this helps! Bye, Ethan > And BTW: > > Does PROGRESS Software have an e-mail address where one can direct > questions and comments to? Would be very nice, but they ever publish one. Not that I know about but THINC has a Email Group for PROGRESS(tm). It is a mailing list for discussion of all relevant aspects of the PROGRESS(tm) RDBMS. Users may subscribe by sending mail to uunet!thinc!progress Coordinator: Ethan A. Lish of THINC (uunet!thinc!ethan) -- Ethan A. Lish ---- 301.652.0651 ---- {uunet}!thinc!ethan Tomorrow's Horizons, Inc.,4807 Bethesda Ave, #330, Bethesda, MD 20814