FW: Code & screen shot - HTML formatted email

[Richard Kreiss]

> -----Original Message-----
> From: Kenneth Brody [mailto:kenbrody at spamcop.net]
> Sent: Thursday, March 18, 2010 2:42 PM
> To: Rkreiss at verizon.net]
> Cc: 'FilePro Mailing List'
> Subject: Re: FW: Code & screen shot - HTML formatted email
> 
> On 3/18/2010 1:58 PM, Rkreiss at verizon.net] wrote:
> > Ken,
> >
> > I put in tbe code as this is an @key function which is the selected from
a list
> box.
> >
> > The problem, as illustrated, happens as soon as the command is executed.
> 
> So, if you run the debugger, the bleed-through occurs immediately after
> executing the MEMO...SHOW statement?
> 
> > Some is different in how memo nn show window works and how the window
> displays using memo nn edit.
> >
> > As i indicatedm only information in dummy fields bleed through.
> [...]
> 
> The problem is that you only show 11 lines of your processing table.
What's
> to say it's not something in one of the multitude of lines that you didn't
> show that are the problem?
> 
> Create a prc table consisting of just those 11 lines (with the addition of
> your @KEY label).  Then, run dclerk with that prc and no automatic
> processing (ie: running with only the 11 lines that you showed us), and
see
> if the still fails.
> 
> If that doesn't fail, then the problem lies elsewhere.
> 
> --
> Kenneth Brody

Ken,

Thanks for your suggestions.

Tested Bill's suggestion that I stop auto processing from running as the
show window comes up first, then auto processing runs causing the bleed
through.

This worked with one caveat, the white line boarder around the window
disappears in sections.

One other question which arose during this test, I used putenv "isshow","y"
in input and then checked it in auto to end the auto processing.

When I used putenv "isshow","N" at @keyC which cleared the memo window, the
value did not change.  Is this value locked for the remainder of this clerk
run or should it have been changed when a new putenv was issued?

Richard