@WEF. @WLF in @ENTSEL

[John Esak]

Sorry Barry,
I put your code exactly as it is in a new table and created screen ADD.
Unfortunately, the way it's written, I can't test whatever it is you want me
to test. All this will allow, whether you go to an existing record or
through Add Records mode, is the viewing of the @entsel message and
subsequent popup, then even if you pass through the @wlfC (I had put all 3
fields on ADD) it breaks out seemingly the same way all the way around.

Maybe you whipped up this sample slightly differently the the actual code.
Can you show it the way you would actually do it... wherein @entsel would
only happen at it's appropriate trigger/time and not every single time it
hits @entsel...  meaning, this is an inescapable loop. I don't know how to
make it do what you want or don't want it to do. It only does what it does.
:-)

John

> -----Original Message-----
> From: filepro-list-bounces+john=valar.com at lists.celestial.com
> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.com] On Behalf
> Of Barry Wiseman
> Sent: Monday, September 24, 2007 8:58 PM
> To: filepro-list at lists.celestial.com
> Subject: RE: @WEF. @WLF in @ENTSEL
> 
> John, here is code to demonstrate the problem.  You should be able to run
> this
> from any file, just create the "ADD" screen with four fields on it, *a *b
> *c
> and *d.  BREAK from the popup will go to @ENTSEL, as long as you haven't
> entered field C, otherwise boom! dclerk exits.
> 
> ::end:
> ::a(2,*,g); b(2,*,g); c(2,*,g); d(2,*,g):
> @ENTSEL::msgbox "Ready to show the popup":
> ::popup update -,"ADD":
> :@sk eq "BRKY":goto @entsel:
> ::msgbox "Popup was saved, now we can do whatever":
> ::end:
> @WEFC::msgbox "Entering field C"; end:
> 
> Quoting John Esak <john at valar.com>:
> 
> > With copyin and such for anti-record locking... not only does it not
> help
> > two users to be in the seme record simultaneously, *but* someone can go
> to
> > the *original* record while you are updating the copy and change *it*.
> No
> > good.
> >
> > I haven't tested your scenario yet Barry, but it sure sounds like a bug
> or
> > such.  If it is, it will be one of the first things I haven't been able
> to
> > do from @entsel successfully... one way or another. :-)
> >
> > Seriously, we do nearly everything from @entsel including huge drill-
> down
> > browses that generate printerd reports, forms, virtually every kind of
> > manipulation and I haven't run into any show-stoppers yet.  I'll try
> what
> > you're talking about... but I'm going to have to read the original note
> > again because the first thing I tried worked as I thought it should.
> I'll
> > let you know.
> >
> > Perhaps, if you put the line of code that creates the problem, I would
> see
> > it immediately.  Sorry to be so dense btw, it's a factor of old age???
> >
> > John
> >
> >
> >
> >> -----Original Message-----
> >> From: filepro-list-bounces+john=valar.com at lists.celestial.com
> >> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.com] On
> Behalf
> >> Of Barry Wiseman
> >> Sent: Monday, September 24, 2007 12:56 PM
> >> To: filepro-list at lists.celestial.com
> >> Subject: Re: @WEF. @WLF in @ENTSEL
> >>
> >> Boaz Bezborodko wrote:
> >>
> >> > If you are so interested in keeping the record out of update mode
> then
> >> > why not work from a separate, duplicate file (or even just a separate
> >> > qualifier)?  When selecting the record to work with COPYIN the data
> to
> >> > the new working record.  Once you're ready to update any particular
> >> > piece of data you update the original record.  The original file is
> only
> >> > open very briefly for the updates.  When you're done you simply
> delete
> >> > the separate working record.
> >>
> >> Actually, that doesn't solve anything; by your scheme, two users still
> >> cannot be in
> >> the same record.  But thanks for the suggestion. :-)
> >>
> >> -----------------------------------------------------------------
> >>   Barry Wiseman                              barry at gensoftdes.com
> >>   Genesis Software Designs, Inc.            Voice: (212) 889-9191
> >>   55 West 45 Street, New York, NY 10036       Fax: (212) 889-1589
> >> -----------------------------------------------------------------
> >>
> >> _______________________________________________
> >> Filepro-list mailing list
> >> Filepro-list at lists.celestial.com
> >> http://mailman.celestial.com/mailman/listinfo/filepro-list
> >
> > _______________________________________________
> > Filepro-list mailing list
> > Filepro-list at lists.celestial.com
> > http://mailman.celestial.com/mailman/listinfo/filepro-list
> >
> >
> 
> 
> 
> --
> Barry Wiseman
> Genesis Software Designs, Inc.
> 55 W 45 Street, New York, NY 10036
> (212) 889-9191    Fax: (212) 889-1589
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list