Re: 4gl RUN statement. No sweat

We find the RUN statement very useful to print documents which need to be printed under multiple conditions. Example : A Policy Certificate (we are an Insurance company) needs to be printed under the following circumstances a. After initial Policy entry b. After modification through any of 10 odd endorsements c. As a batch process (rarely!) Rather than 'load' the many individual 4gis with the common report function, we RUN the report 4gi with the policy number as a parameter. It works perfectly. Our security application (which a user initially confronts after logging in) which controls our users access to the various insurance application 4gis also uses the RUN statement with abandon. However, the security application resides in a different database from that of the insurance application. Again, we have no problems at all. Cheers, >Randy Sylvester <rcs@pc_randys.triad.com> wrote: > > >: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." >:I am working in an environment where several applications that >:access a database are using the RUN statement to execute another >:4gl that accesses a database and it appears to work (there is no >:CLOSE DATABASE statement). I called tech support to elaborate on >:why this should not be done and there response was "unpredictable >:results may occur". > >:I am concerned that, even though it appears to work, we may >:be doing something that might be degrading the overall performance >:of the engine. Does anyone have any insights on this situation??? ---------------------- Rudy Fernandes GIC, KUWAIT ----------------------