empty records?

Fairlight fairlite at fairlite.com
Mon Jul 9 16:55:55 PDT 2018 

Well, it's definitely -not- Curad[tm], because it's definitely not ouchless.

That reads like a really half-arsed series of 'fixes' which weren't
adequately planned.  I cringe just reading it.

Instead of devising and implementing something which addressed the original
issue without inducing side effects, they just bunged a flawed 'fix' in
there anyway, tossed in a new variable, and made users choose between the
lesser of two evils.

What happens when those two modes become mutually exclusive goals for a
single user, as undoubtedly must be the case?

*shakes head sadly*

m->


On Mon, Jul 09, 2018 at 05:52:00PM -0400, Jose Lerebours via Filepro-list thus spoke:
> lol - Is this an old fashion band aid or a liquid band aid?
> 
> 
> On 07/09/2018 03:25 PM, Robert Haussmann via Filepro-list wrote:
> >Thanks again for everyone's input.  Per fPTech, the temporary workaround is to set PFOLDWIRTE=ON.
> >
> >I confirmed that, with this env variable set, the process behaves as expected (no blank record added) on all verions of fP.
> >
> >I wasn't familiar with this variable--for those interested, I found the following entries in the readme that mention PFOLDWRITE:
> >
> >Task #1526 (All)
> >Problem caused by a fix last March. Work-around was to use
> >PFOLDWRITE=ON, but that caused a conflict:
> >dreport eee -f export_csv -a -ro
> >Now, PFOLDWRITE is not necessary since pfcb will not be marked
> >dirty IF offending code is reached from *report and -ro is used.
> >
> >Task #1509
> >Fixed dummy fields disappearing off of the screen after a WRITE and END
> >combo if a record has not been changed. Added PFOLDWRITE to revert to
> >old method in case of issues, default OFF.
> >
> >Bob
> >
> >>-----Original Message-----
> >>From: Filepro-list [mailto:filepro-list-
> >>bounces+haussma=nextdimension.net at lists.celestial.com] On Behalf Of
> >>Jose Lerebours via Filepro-list
> >>Sent: Monday, July 09, 2018 3:01 PM
> >>To: filepro-list at lists.celestial.com
> >>Subject: Re: empty records?
> >>
> >>Well, there is only so much one can do ... if fp run time is not making it
> >>possible we are then left with "wait for glitch fix".
> >>
> >>Thanks for the reply, I am sure others following this will benefit from your
> >>reporting on your findings!
> >>
> >>
> >>On 07/09/2018 02:51 PM, Bruce Easton via Filepro-list wrote:
> >>>In my case under 5.6.06, Jose, ESC ESC of the popup, then testing @sk
> >>>eq "BRKY" to then just executing "exit" saved the new record being
> >>>used to stand on.  (Absolutely no "end" statement in this flow,
> >>>[explicit end or assumed end].)
> >>>
> >>>But yes, performing the delete prior to exiting does delete the temp
> >>>record, so that works for this technique at least under 5.6.06.
> >>>
> >>>Bruce
> >>>
> >>>On 7/9/18 2:26 PM, Jose Lerebours via Filepro-list wrote:
> >>>>It makes no difference if you populate a bunch of dummy fields or
> >>>>real fields, "ESC ESC" and "END" will save the record ...
> >>>>
> >>>>In lieu of "END", use "screen" command to place cursor ... the key
> >>>>here is to never reach the "END" command if you do not wish to save
> >>>>blank records (multiple per session very possibly).
> >>>>
> >>>>I figure you have an "X" to exit off the browse lookup or checking
> >>>>for BRKY to see if user presses DEL DEL to break out ... in this
> >>>>case, simply do "DELETE; EXIT" and see what happens.
> >>>>
> >>>>
> >>>>
> >>>>On 07/09/2018 01:56 PM, Bruce Easton via Filepro-list wrote:
> >>>>>I needed to work on something related to this today, so I wanted to
> >>>>>share my findings. Keep in my  - this is on Windows filepro version
> >>>>>5.6.06.  Originally I was trying to just run from @menu to browse
> >>>>>another file and then popup update to collect data using a popup
> >>>>>screen on the current file that only has dummy fields on it.  I had
> >>>>>forgotten that you can't do this (filepro still thinks you're
> >>>>>attempting to update something on the current record even though in
> >>>>>this case it is just dummy fields that I want to ultimately write
> >>>>>somewhere else - not to the current record).
> >>>>>
> >>>>>Ergo the need to use the add-record mode technique to stand on a new
> >>>>>record.  So I changed the code to use @wef while standing on the new
> >>>>>record (-xa flag from the script line), and it works OK, but what I
> >>>>>noticed was this:  If I bail out before doing a popup or if I do the
> >>>>>popup but cancel out of the popup (where processing leads to an
> >>>>>"exit" command), the new record being used to stand on for this
> >>>>>purpose is not saved, but if I save the popup (of dummy fields), and
> >>>>>then bail out of the program with cancel, the new record is saved.
> >>>>>This actually seems consistent from the point of view that filepro
> >>>>>thinks that any popup update (of the type "-" for the current file)
> >>>>>is an attempt to update the current record whether it has only dummy
> >>>>>fields or real fields on it.
> >>>>>
> >>>>>I'm not sure if this behavior is consistent with previous versions,
> >>>>>but I know I'd want to see all of Bob's code to know if there was
> >>>>>something different  - at least between versions 5.6 and 5.8.
> >>>>>
> >>>>>
> >>>>>
> >>>>>On 7/6/18 10:01 PM, Jose Lerebours via Filepro-list wrote:
> >>>>>>I am blown away to hear this ... I've used this technique for as
> >>>>>>long as I can remember and the norm, as I understand it is/was,
> >>>>>>"exit" prior to "end" does not save the record.
> >>>>>>
> >>>>>>This has proven very handy for many quick processing where as
> >>>>>>
> >>>>>>*aa in a screen and
> >>>>>>
> >>>>>>@wef* in a processing table (I normally use a unique processing
> >>>>>>table for each need/task so -z and -y are always invoked)
> >>>>>>
> >>>>>>and parameter -xa to place in add record mode, which of course,
> >>>>>>triggers @wef* ...
> >>>>>>
> >>>>>>
> >>>>>>This is likely a BUG on this version - I just cannot imagine fp
> >>>>>>changing this out of the blues without notice.   So, how much do
> >>>>>>you get for finding a BUG?  A free upgrade or must you pay for the
> >>>>>>version that addresses this BUG as well? ;-) lol   I say, even if
> >>>>>>you are not "subscribed" for free upgrades, you are entitle to a
> >>>>>>FREE ONE!
> >>>>>>
> >>>>>>Nice find / great work ... Thanks!!!
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>On 07/06/2018 08:02 PM, Robert Haussmann via Filepro-list wrote:
> >>>>>>>Yep, this is indeed what is happening. It goes to a different
> >>>>>>>section where it writes out a text file and then exists.  But the
> >>>>>>>conclusion is the same--whereas previous versions of fP didn't
> >>>>>>>save the blank record on "exit", 5.8.00.15 does.
> >>>>>>>
> >>>>>>>Bob
> >>>>>>>
> >>>>>>>>-----Original Message-----
> >>>>>>>>From: Filepro-list [mailto:filepro-list-
> >>>>>>>>bounces+haussma=nextdimension.net at lists.celestial.com] On
> >>Behalf Of
> >>>>>>>>Bruce Easton via Filepro-list
> >>>>>>>>Sent: Friday, July 06, 2018 7:38 PM
> >>>>>>>>To: filepro-list at lists.celestial.com
> >>>>>>>>Subject: Re: empty records?
> >>>>>>>>
> >>>>>>>>Perhaps the execution is never getting back up to the start label
> >>>>>>>>for some
> >>>>>>>>reason.  I would recommend setting up a session in debug to see
> >>>>>>>>where it
> >>>>>>>>goes when the user saves their input.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>On 7/6/18 7:32 PM, Robert Haussmann via Filepro-list wrote:
> >>>>>>>>>Actually records aren't added through this method (I add the
> >>>>>>>>>records via a
> >>>>>>>>standard rclerk instance with a different screen number).
> >>>>>>>>>Yes, you are absolutely right-- it would be better not to have
> >>>>>>>>>to sit on any
> >>>>>>>>record.  I haven't considered using @menu--I'll have to give that
> >>>>>>>>some
> >>>>>>>>thought.
> >>>>>>>>>Just tried the pushkey suggestion (both single and double), but
> >>>>>>>>>no joy...
> >>>>>>>>>
> >>>>>>>>>Bob
> >>>>>>>>>
> >>>>>>>>>>-----Original Message-----
> >>>>>>>>>>From: Filepro-list [mailto:filepro-list-
> >>>>>>>>>>bounces+haussma=nextdimension.net at lists.celestial.com] On
> >>>>>>>>>>Behalf Of
> >>>>>>>>>>Bruce Easton via Filepro-list
> >>>>>>>>>>Sent: Friday, July 06, 2018 7:23 PM
> >>>>>>>>>>To: filepro-list at lists.celestial.com
> >>>>>>>>>>Subject: Re: empty records?
> >>>>>>>>>>
> >>>>>>>>>>The technique used there begs more questions.  (I would
> >>wonder,
> >>>>>>>>>>for
> >>>>>>>>>>instance, what happens to the record after it's been added -
> >>>>>>>>>>what is
> >>>>>>>>>>it used for and what it's supposed to retain..   Is it possible
> >>>>>>>>>>that
> >>>>>>>>>>it would be better designed to not sit on any record, say from
> >>>>>>>>>>@menu,
> >>>>>>>>>>while it's verifying that it has acceptable input...)
> >>>>>>>>>>
> >>>>>>>>>>But I see your point.  It's odd that it behaves differently
> >>>>>>>>>>now. You
> >>>>>>>>>>could try this instead for the first line:
> >>>>>>>>>>
> >>>>>>>>>>start  If: 1 eq ""
> >>>>>>>>>>        Then: pushkey "[BRKY][BRKY]"; end   '(or just one BRKY for
> >>>>>>>>>>Windows I
> >>>>>>>>>>think)
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>On 7/6/18 6:59 PM, Robert Haussmann via Filepro-list wrote:
> >>>>>>>>>>>Yes, I use "start" as the label. This code as actually written
> >>>>>>>>>>>like
> >>>>>>>>>>>2 decades(!)
> >>>>>>>>>>ago, so I'm having a little difficulty remembering. But it looks
> >>>>>>>>>>like the general flow is:
> >>>>>>>>>>>@wef1 label ensures we are on the right screen #, if so go to
> >>>>>>>>>>>the "login"
> >>>>>>>>>>label, if not end:
> >>>>>>>>>>>12  -------   -   -   -   -
> >>>>>>>>>>>@wef1  ? If: @sn eq "9"
> >>>>>>>>>>>           Then: goto login
> >>>>>>>>>>>     13  -------   -   -   -   -
> >>>>>>>>>>>           ? If:
> >>>>>>>>>>>           Then: end
> >>>>>>>>>>>     14  -------   -   -   -   -
> >>>>>>>>>>>
> >>>>>>>>>>>"login" is where we input username/password and check that
> >>>>>>>>>>>they are
> >>>>>>>>>>valid.
> >>>>>>>>>>>The actual processing itself (after some comments and variable
> >>>>>>>>>>declarations) is here (the "Start" label):
> >>>>>>>>>>>start  ? If: 1 eq ""
> >>>>>>>>>>>           Then:  exit                      'do not save blank
> >>>>>>>>>>>records
> >>>>>>>>>>>     11  -------   -   -   -   -   -   -   -   - - -   -   -
> >>>>>>>>>>>-   -   -   -
> >>>>>>>>>>>
> >>>>>>>>>>>>-----Original Message-----
> >>>>>>>>>>>>From: Filepro-list [mailto:filepro-list-
> >>>>>>>>>>>>bounces+haussma=nextdimension.net at lists.celestial.com] On
> >>Behalf
> >>>>>>>>Of
> >>>>>>>>>>>>Bruce Easton via Filepro-list
> >>>>>>>>>>>>Sent: Friday, July 06, 2018 6:55 PM
> >>>>>>>>>>>>To: filepro-list at lists.celestial.com
> >>>>>>>>>>>>Subject: Re: empty records?
> >>>>>>>>>>>>
> >>>>>>>>>>>>Just curious - is there a label on that first line? (More
> >>>>>>>>>>>>importantly a filepro reserved word event trigger?) I'm just
> >>>>>>>>>>>>wondering how the program is supposed to test that first line
> >>>>>>>>>>>>prior
> >>>>>>>>>>>>to an "SAVE" or "CANCEL" coming
> >>>>>>>>>>from
> >>>>>>>>>>>>the user or the program...
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>On 7/6/18 6:46 PM, Robert Haussmann via Filepro-list wrote:
> >>>>>>>>>>>>>Bruce and Jose--thank you both for your suggestions.  I think I
> >>>>>>>>>>>>>found out
> >>>>>>>>>>>>what's going on.  The one database is used for security
> >>>>>>>>>>>>(contains a
> >>>>>>>>>>>>list of usernames, pw's and access rights).  We go into this
> >>>>>>>>>>>>with
> >>>>>>>>>>>>"rclerk security -
> >>>>>>>>>>s9 -
> >>>>>>>>>>>>xa -d", and then the processing inputs
> >>username+password.  The
> >>>>>>>>>>>>first line
> >>>>>>>>>>in
> >>>>>>>>>>>>input processing is:
> >>>>>>>>>>>>>If: 1 eq ""
> >>>>>>>>>>>>>Then: exit
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>Well, it seems that in 5.8.00.08, things work as expected.
> >>>>>>>>>>>>>But in
> >>>>>>>>>>5.8.00.15,
> >>>>>>>>>>>>this results in a new record being saved. (not sure when this
> >>>>>>>>>>>>behavior was introduced, as I don't have the interim versions
> >>>>>>>>>>>>available
> >>>>>>>>to test.).
> >>>>>>>>>>>>>Bob
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>>-----Original Message-----
> >>>>>>>>>>>>>>From: Filepro-list [mailto:filepro-list-
> >>>>>>>>>>>>>>bounces+haussma=nextdimension.net at lists.celestial.com]
> >>On
> >>>>>>>>Behalf
> >>>>>>>>>>Of
> >>>>>>>>>>>>>>Robert Haussmann via Filepro-list
> >>>>>>>>>>>>>>Sent: Friday, July 06, 2018 6:32 PM
> >>>>>>>>>>>>>>To: Bruce Easton <bruce at stn.com>; 'Filepro List'
> >>>>>>>>>>>>>><filepro-list at celestial.com>
> >>>>>>>>>>>>>>Subject: RE: empty records?
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>Thanks--I've definitely run into this before (where
> >>>>>>>>>>>>>>basically it
> >>>>>>>>>>>>>>keeps adding records until you kill the process). That's
> >>>>>>>>>>>>>>not the
> >>>>>>>>>>>>>>case here--these are getting added one at a time it seems
> >>>>>>>>>>>>>>(in a
> >>>>>>>>>>>>>>day I might see anywhere between 20 and
> >>>>>>>>>>>>>>200 new records).  It is the strangest thing. I have to
> >>>>>>>>>>>>>>believe
> >>>>>>>>>>>>>>it is related to the updated version....
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>Bob
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>-----Original Message-----
> >>>>>>>>>>>>>>>>From: Filepro-list [mailto:filepro-list-
> >>>>>>>>>>>>>>>>
> >>bounces+haussma=nextdimension.net at lists.celestial.com] On
> >>>>>>>>>>Behalf
> >>>>>>>>>>>>Of
> >>>>>>>>>>>>>>>>Bruce Easton via Filepro-list
> >>>>>>>>>>>>>>>>Sent: Friday, July 06, 2018 6:23 PM
> >>>>>>>>>>>>>>>>To: filepro-list at lists.celestial.com
> >>>>>>>>>>>>>>>>Subject: Re: empty records?
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>The only thing I've seen that can cause this if you have
> >>>>>>>>>>>>>>>>screens that have no field on them that can be updated,
> >>and
> >>>>>>>>>>>>>>>>they you allow access to users to get to any of those
> >>>>>>>>>>>>>>>>screens with
> >>>>>>>>'Add Records'
> >>>>>>>>>>mode.
> >>>>>>>>>>>>>>>>Bruce
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>On 7/6/18 6:17 PM, Robert Haussmann via Filepro-list
> >>wrote:
> >>>>>>>>>>>>>>>>>Has anyone encountered an issue with fP in which
> >>completely
> >>>>>>>>>>empty
> >>>>>>>>>>>>>>>>records are created seemingly at random?  We are seeing
> >>what
> >>>>>>>>>>>>>>>>appears to be phantom blank records getting inserted into
> >>>>>>>>>>>>>>>>specific filepro
> >>>>>>>>>>>>>>>databases.
> >>>>>>>>>>>>>>>>These dbs have run for years with no problem-the only
> >>change
> >>>>>>>>>>>>>>>>recently was updating from 5.8.00.03 to 5.8.00.15
> >>(Windows
> >>>>>>>>version).
> >>>>>>>>>>>>>>>>I'm honestly not even sure where to start looking-as I
> >>noted
> >>>>>>>>>>>>>>>>these apps ran for years (decades, really) without issue.
> >>>>>>>>>>>>>>>>>Thanks,
> >>>>>>>>>>>>>>>>>Bob Haussmann
> >>>>>>>>>>>>>>>>>-------------- next part -------------- An HTML
> >>>>>>>>>>>>>>>>>attachment was
> >>>>>>>>>>>>>>>>>scrubbed...
> >>>>>>>>>>>>>>>>>URL:
> >>>>>>>>>>>>>>>>><http://mailman.celestial.com/pipermail/filepro-
> >>>>>>>>>>list/attachments/2
> >>>>>>>>>>>>>>>>>01
> >>>>>>>>>>>>>>>>>80
> >>>>>>>>>>>>>>>>>706/dda5e6f2/attachment.html>
> >>>>>>>>>>>>>>>>>
> >>_______________________________________________
> >>>>>>>>>>>>>>>>>Filepro-list mailing list
> >>>>>>>>>>>>>>>>>Filepro-list at lists.celestial.com
> >>>>>>>>>>>>>>>>>Subscribe/Unsubscribe/Subscription Changes
> >>>>>>>>>>>>>>>>>http://mailman.celestial.com/mailman/listinfo/filepro-
> >>list
> >>>>>>>>>>>>>>>>---
> >>>>>>>>>>>>>>>>This email has been checked for viruses by Avast antivirus
> >>>>>>>>software.
> >>>>>>>>>>>>>>>>https://www.avast.com/antivirus
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>_______________________________________________
> >>>>>>>>>>>>>>>>Filepro-list mailing list
> >>>>>>>>>>>>>>>>Filepro-list at lists.celestial.com
> >>>>>>>>>>>>>>>>Subscribe/Unsubscribe/Subscription Changes
> >>>>>>>>>>>>>>>>http://mailman.celestial.com/mailman/listinfo/filepro-list
> >>_______________________________________________
> >>>>>>>>>>>>>>Filepro-list mailing list
> >>>>>>>>>>>>>>Filepro-list at lists.celestial.com
> >>>>>>>>>>>>>>Subscribe/Unsubscribe/Subscription Changes
> >>>>>>>>>>>>>>http://mailman.celestial.com/mailman/listinfo/filepro-list
> >>>>>>>>>>>>>_______________________________________________
> >>>>>>>>>>>>>Filepro-list mailing list
> >>>>>>>>>>>>>Filepro-list at lists.celestial.com
> >>>>>>>>>>>>>Subscribe/Unsubscribe/Subscription Changes
> >>>>>>>>>>>>>http://mailman.celestial.com/mailman/listinfo/filepro-list
> >>>>>>>>>>>>>
> >>>>>>>>>>>>_______________________________________________
> >>>>>>>>>>>>Filepro-list mailing list
> >>>>>>>>>>>>Filepro-list at lists.celestial.com
> >>>>>>>>>>>>Subscribe/Unsubscribe/Subscription Changes
> >>>>>>>>>>>>http://mailman.celestial.com/mailman/listinfo/filepro-list
> >>>>>>>>>>>_______________________________________________
> >>>>>>>>>>>Filepro-list mailing list
> >>>>>>>>>>>Filepro-list at lists.celestial.com
> >>>>>>>>>>>Subscribe/Unsubscribe/Subscription Changes
> >>>>>>>>>>>http://mailman.celestial.com/mailman/listinfo/filepro-list
> >>>>>>>>>>_______________________________________________
> >>>>>>>>>>Filepro-list mailing list
> >>>>>>>>>>Filepro-list at lists.celestial.com
> >>>>>>>>>>Subscribe/Unsubscribe/Subscription Changes
> >>>>>>>>>>http://mailman.celestial.com/mailman/listinfo/filepro-list
> >>>>>>>>>_______________________________________________
> >>>>>>>>>Filepro-list mailing list
> >>>>>>>>>Filepro-list at lists.celestial.com
> >>>>>>>>>Subscribe/Unsubscribe/Subscription Changes
> >>>>>>>>>http://mailman.celestial.com/mailman/listinfo/filepro-list
> >>>>>>>>
> >>>>>>>>_______________________________________________
> >>>>>>>>Filepro-list mailing list
> >>>>>>>>Filepro-list at lists.celestial.com
> >>>>>>>>Subscribe/Unsubscribe/Subscription Changes
> >>>>>>>>http://mailman.celestial.com/mailman/listinfo/filepro-list
> >>>>>>>_______________________________________________
> >>>>>>>Filepro-list mailing list
> >>>>>>>Filepro-list at lists.celestial.com
> >>>>>>>Subscribe/Unsubscribe/Subscription Changes
> >>>>>>>http://mailman.celestial.com/mailman/listinfo/filepro-list
> >>>>>>_______________________________________________
> >>>>>>Filepro-list mailing list
> >>>>>>Filepro-list at lists.celestial.com
> >>>>>>Subscribe/Unsubscribe/Subscription Changes
> >>>>>>http://mailman.celestial.com/mailman/listinfo/filepro-list
> >>>>>
> >>>>>
> >>>>>
> >>>>>---
> >>>>>This email has been checked for viruses by Avast antivirus software.
> >>>>>https://www.avast.com/antivirus
> >>>>>
> >>>>>_______________________________________________
> >>>>>Filepro-list mailing list
> >>>>>Filepro-list at lists.celestial.com
> >>>>>Subscribe/Unsubscribe/Subscription Changes
> >>>>>http://mailman.celestial.com/mailman/listinfo/filepro-list
> >>>>_______________________________________________
> >>>>Filepro-list mailing list
> >>>>Filepro-list at lists.celestial.com
> >>>>Subscribe/Unsubscribe/Subscription Changes
> >>>>http://mailman.celestial.com/mailman/listinfo/filepro-list
> >>>
> >>>
> >>>_______________________________________________
> >>>Filepro-list mailing list
> >>>Filepro-list at lists.celestial.com
> >>>Subscribe/Unsubscribe/Subscription Changes
> >>>http://mailman.celestial.com/mailman/listinfo/filepro-list
> >>_______________________________________________
> >>Filepro-list mailing list
> >>Filepro-list at lists.celestial.com
> >>Subscribe/Unsubscribe/Subscription Changes
> >>http://mailman.celestial.com/mailman/listinfo/filepro-list
> >_______________________________________________
> >Filepro-list mailing list
> >Filepro-list at lists.celestial.com
> >Subscribe/Unsubscribe/Subscription Changes
> >http://mailman.celestial.com/mailman/listinfo/filepro-list
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list

-- 
Audio panton, cogito singularis.

More information about the Filepro-list mailing list