Hi there.

I'm running into a problem with editing a MORE on a report. I'm working with Dev Studio 8001m.

I started with the following case:

 
 TABLE FILE EMPDATA
 PRINT
 EMPDATA.EMPDATA.SALARY
 ON TABLE SET PAGE-NUM NOLEAD
 
 ON TABLE NOTOTAL
 ON TABLE HOLD AS HOLD1 FORMAT ALPHA
 ON TABLE SET HTMLCSS ON
 ON TABLE SET STYLE *
 INCLUDE = endeflt,
 $
 ENDSTYLE
 END
 TABLE FILE EMPLOYEE
 PRINT
 EMPLOYEE.PAYINFO.SALARY
 ON TABLE SET PAGE-NUM NOLEAD
 ON TABLE NOTOTAL
 ON TABLE PCHOLD FORMAT HTML
 ON TABLE SET HTMLCSS ON
 ON TABLE SET STYLE *
 INCLUDE = endeflt,
 $
 ENDSTYLE
 MORE
 FILE HOLD1
 END
  

This works as expected. When I re-open it in Developer Studio and select the final report, I see the following as the source:

   TABLE FILE EMPLOYEE
 PRINT
 EMPLOYEE.PAYINFO.SALARY
 ON TABLE SET PAGE-NUM NOLEAD
 ON TABLE NOTOTAL
 ON TABLE PCHOLD FORMAT HTML
 ON TABLE SET HTMLCSS ON
 ON TABLE SET STYLE *
 INCLUDE = endeflt,
 $
 ENDSTYLE
 MORE
 FILE HOLD1
 END

Again, this is as expected and it works.

However, if I hit the universal concatenation button again and then take any action (click OK, cancel or anything else), when I revisit the source, it has changed:

  TABLE FILE HOLD1
 PRINT
 EMPLOYEE.PAYINFO.SALARY
 ON TABLE SET PAGE-NUM NOLEAD
 ON TABLE NOTOTAL
 ON TABLE PCHOLD FORMAT HTML
 ON TABLE SET HTMLCSS ON
 
 ON TABLE SET STYLE *
 INCLUDE = endeflt,
 $
 ENDSTYLE
 MORE
 FILE HOLD1
 END
 

Note that in the first row, the TABLE FILE has changed from EMPLOYEE to HOLD1. I'm now unable to run the report. I can exit the report without saving and it reverts to the correct source, but that's all.

Am I misusing the functionality? Is there something else I should be doing?

This message has been edited. Last edited by: <Kathryn Henning>,

"Doctor, it hurts when I do this."

"Then stop doing this."

You have stumbled across a Bug in the editor tool. I humbly recommend you go after changes in this unit by selecting "Edit in Text Editor" and scrolling down to the appropriate section of source code. It's pretty obvious you have a handle on what's going on in the source code so you should be able to make this work to your advantage.

J.

John,

Thanks for the reply. I wasn't sure if it was a bug or something I was doing wrong. I opened a case about it as well & was sent an example of how MORE should work in response. I wasn't clear if it was user error on my part, so I'm glad to hear that it looks like it was not.