Re: 4gl RUN statement

>:On page 3-264 of the 4gl Reference, Volume I, Version 6.0 >:it states inregards to the RUN statement, "You can even run >:a second 4gl application as a secondary process, provided that >:only one of the 4gl applications accesses a database." > >Isn't this a documentation bug? >Isn't run supposed to execute a program so it becomes a completely >separate program that can do anything it want completely independent >of the program with the run statement? >If this isn't the case you can at least call a small C-function that >execute your 4GL program in this way. See the archives at www.iiug.org >for an excample of such a program. This is a documentation error. I think the authors were trying to communicate that the database connection will not be maintained in a RUN statement *because* it runs as a completely independent program. One of the ramifications of this independence is that if you choose to invoke another process it will count as another user against the number of licenses you have purchased. For that reason you must be careful about how you choose to implement "recursive" database access programs. I have seen an instance where the customer ran out of licenses on a 32 license machine when only 10 people were sitting at the terminals. This same caution applies also to ISQL menus and other applications, too. Though it is wise to ask for a "sanity check" when you think you've found a documentation error, once you're sure it is an error then there is a procedure for reporting the flaw. At the front of every manual there is an email address and a paragraph detailing how to notify Informix of documentation problems. Please don't just mark up your manuals, help the documentation team to build a better product by pointing out flaws and how to correct them. Happy hunting, ______________________________________________________ Clem Akins (aka clema@informix.com) Informix Software, Inc (Standard disclaimers apply) International Technical Support Last seen: Singapore, home of the Merlion