Browse lookup

[Richard Kreiss]

> -----Original Message-----
> From: Kenneth Brody [mailto:kenbrody at spamcop.net]
> Sent: Saturday, October 11, 2014 11:34 AM
> To: Richard Kreiss
> Cc: Richard Kreiss; filepro-list at lists.celestial.com
> Subject: Re: Browse lookup
> 
> On 10/10/2014 9:01 PM, Richard Kreiss wrote:
> > Top post.
> >
> > Closing the first and opening the second is what I want.
> 
> Okay.  Just verifying that you realized that would happen.
> 
> > The second
> > browse is only for the person(s) calling in. The problem is after the
> > first person's event date is selected and the current browse is
> > re-executed, the header, color, and frame disappear. When returning to
> > the original browse and a new person is selected the second browse
> > displays properly until the date is selected and the browse is
> > re-executed.
> >
> > One thing I omitted, this is being done through RDP.
> 
> Doesn't matter, unless there is an RDP bug affecting how it shows filePro
> browse lookup windows remotely, while being correct locally.
> 
> > Chk_dat checks to see if the person is already signed up for an event.
> 
> So no screen changes?
> 
> > The other pops up a list box of event dates for the events being held
> > for that doctor.
> 
> "Pops up a list" how?  I am assuming LISTBOX(), but you don't explicitly say
> so.
> 
> > Once the date number has been selected, the date is posted to an event
> > record. Once that occurs the operator can ask if any guests are being
> > brought an how many. That value is posted to the event record.
> 
> What sort of screen interactions take place there?
> 
> If you single-step the processing in the debugger, at what point does the
> screen get "messed up"?

Ken,

After thinking about this problem a bit more, I tested a clearb prior to the second browse opening.  This did two things:
	1. it insured that the first browse closed properly
	2. It closed the second browse and then reopened it on re-execution of the browse.

This is the workaround for the problem.  I still don't know why the problem started.

Richard