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 18 JUN 1998 07:05:41PM Tracy Kaltenbrun at ABC-Clio wrote:

We have encountered two problems since installing the

3.12 upgrade. Both seem to be related to printing.

Our setup is:

Novell 4.11, NLM (not upgraded to 1.5 yet)

Windows 95 workstations (mostly), 25 users

In one case, several programs which produce a printed

report end with the message "Press Enter for next

page or Escto end listing". After pressing either

Enter or Esc, the program returns OK, and goes back to

the menu. But it wasn't there before.

The other problem also occurs at the end of a program

which also produces print output,

but only after the program has returned to the menu.

(So possibly not a print-related problem?)

In that case, when the user enters escape to go back

to a previous menu, they get the TCL window, and cannot

escape from that window. The only way to cleanly exit

from AREV is to enter OFF in the TCL window.

Any suggestions for fixing either of these programs?

Anybody else experience similar problems? We are mostly

Windows 95 workstations but the same problem occurs on

DOS workstations.

Thanks for any help.

Tracy


At 18 JUN 1998 11:04PM Matt Sorrell wrote:

I don't know about your first problem, but the second I think I can help with.

I had this problem in a program I wrote one time, but I don't think it was 3.12 specific. The problem was the program I was running from the menu was a cataloged subroutine (code 'S'). In the program, I was mistakenly using 'STOP' commands instead of 'RETURN' commands. When my program encountered the 'STOP', it immediately ceased all execution, including the calling program which in this case was the menu. It caused some very strange behavior.

Hope this helps and I'm not just coming from left field here.

Matt


At 20 JUN 1998 02:56PM Tracy Kaltenbrun, ABC-Clio wrote:

Matt,

Thanks for the suggestion. This doesn't appear to be

the problem with our program, however.

Tracy


At 27 JUN 1998 03:53PM Aaron Kaplan wrote:

Matt's suggestion was pretty much on target. In 3.12, we cleaned up a lot of bad code floating about in the system. With that, we enforced a few thinks that, while always docced as required, really weren't.

One of those is that any program that calls INIT.VIEW must be a main program and not a subroutine. Before that, a developer could fudge around and still get it to work. 3.12 make this much more difficult, if not impossible to do.

Another thing were some changes inside RTP18 which handles heading and footing and how this relates to PRINTER OFF and turning off INIT.VIEW. I can't remember which is which anymore, but i think you may be

nulling these values out before setting PRINTER OFF. It's either that or the other way, so just reverse whatever you are doing.

What's happening is that you've diabled the output viewer, but RTP18 is still getting called. There are other ways to handle this, with HEADING.CONTROL and possibly even calling RTP18 directly, but you shouldn't have to do this.

akaplan@sprezzatura.com

Sprezzatura, Inc.

www.sprezzatura.com_zz.jpg

View this thread on the forum...

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