Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 17 JAN 2000 05:35:57AM Pete wrote:

I get the following message :

Line 1 'RTP18.English' broke because a run time error was encountered.

I am creating a batch reporting module which will export reports to text files using the PDISK command. There are 24 reports. Using the r commnad in the debugger, I can see the problem is caused by one particular large report. I do not get this message when I exclude this report. However, I need to print this problem report. I can print this problem report by itself but I still sometimes get the above error message.

Any ideas what is causing this problem? Is it a DOS memory problem?


At 17 JAN 2000 08:23AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

What is the runtime error?

Does the error happen if you move this report to the front of the list?

How are you calling the reports?

The Sprezzatura Group

World leaders in all things RevSoft

www.sprezzatura.com_zz.jpg


At 17 JAN 2000 08:24PM Pete wrote:

The error message is:

Line 5 'RTP18.English' broke because a run time error was encountered

The problem report is actually the first one in the batch.

All of the report details are kept in a parameter file. I will loop through the parameter file. On each loop I will do the following:

 NO.OF.ID=COUNT(ID_LIST,@VM) + 1
 FOR XX=1 TO NO.OF.ID
    READ REC FROM MASTER.RPT.PARAM,ID_LIST ELSE GO 9000
    RPT.CODE  =TRIM(REC)    ;* REPORT CODE        
    RPT.NAME  =TRIM(REC)    ;* REPORT NAME        
    RPT.FILE  =TRIM(REC)    ;* REPORT FILE        
    RPT.DIR   =TRIM(REC)    ;* REPORT DIRECTORY   
    RPT.PGM   =TRIM(REC)    ;* PROGRAM FILE       
    RPT.PGM.ID=TRIM(REC)    ;* PROGRAM NAME       
    RPT.PARAM =TRIM(REC)    ;* PROGRAM PARAMETERS 
    EXP.PATH  =RPT.DIR:'\':RPT.FILE
    CMD       =RPT.PGM:' ':RPT.PGM.ID:' ':RPT.PARAM
    PRINT @(0,21):HIGH:'Printing ':RPT.NAME'L#40':EOL
    PERFORM 'PDISK ':EXP.PATH:' (O'
    PERFORM 'RUN ':CMD
 NEXT XX

I basically do a PDISK then I run the report with the (P parameter which will re-direct the output to the printer.

I am running the program via MD-DOS


At 17 JAN 2000 08:35PM Pete wrote:

The error message I get when I look at the text file containing the report is:

'RTP19' Line 1. B28 Not enough string space - Out of Memory.


At 17 JAN 2000 10:27PM PETE wrote:

I think I found the problem. The report was always falling over on a certain record. The size of this record is 32K. Since I am currently running the report module in our test environment I can delete this record. I did not encounter this problem after deleting this record.

It is unlikely that we would get a record this big in our production environment, however, if there is one, then I am pretty certain the report will fall over.

It there anything I can do to increase memory on a MS-DOS environment?


At 18 JAN 2000 09:20AM Don Miller - C3 Inc. wrote:

Pete…

I assume that you are running under Win95/98. Check the obvious things:

Make sure EMS is enabled on the workstation by checking the Memory Tab on the shortcut. If no EMS is available, then the whole thing has to run in conventional memory. Depending on how the environment is set up, you can have less than 560K of conventional memory. This can cause the kind of error you are getting. If EMS is available, limit the amount of EMS to 4096 in the EMS dropdown, Disable XMS and uncheck the Uses High Memory Area check box. Start your app with:

AREV /M4096X.

If you are in plain-vanilla MS-DOS, then you have to spend some time fiddling with the CONFIG.SYS / AUTOEXEC.BAT parameters in order to maximize conventional memory.

HTH

Don Miller

C3 Inc.

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/345a9ca489235bb885256869003a3923.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1