Memo magic is really distressing filepro user

[John Esak]

> > If you want to see why this is required at the 5.0.13 level
> > of filePro, check on the filePro Survivor CD's. One of the
> > lessons in the chapter on MEMO shows your example with and
> > without the WRITE and what happens. It may apply to what is
> > happening to you. I will assume since I submitted this as a
> > bug report that the problem was fixed after 5.0.14, since it
> > was still there then. Haven't checked in 5.0.6, but I will
> > shortly and let everyone know.
> > (I believe you bought the Survivor Series... a few Tony's
> > did... and I seem to remember an "Old Tony" in there... :-)
> >
> > John
> I have found that ANY data entry, to the current record/file, done at @key
> will not hold unless a write is executed just before the END.
>
> I will assume that since there is no save/escape executed when the @key
> routine hits an end command, the record is left as it was.  One needs to
> force the write to lock in any changes to the record that are made.
>
> Richard Kreiss
> GCC Consulting
>
>
>
> >
> > > -----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 Tony Freehauf
> > > Sent: Friday, August 04, 2006 10:07 AM
> > > To: filepro-list at lists.celestial.com
> > > Subject: Memo magic is really distressing filepro user
> > >
> > >
> > > Memo erases sometimes-why (its like magic) I thought my blob woes
> > > where gone when I discovered blobfix.
> > > Well blobfix takes memo's from not working to working.
> > > But now
> > > Sometimes
> > > When the user goes into the blob the blob information disappears.
> > > No error message appears.
> > > The data is just gone.
> > > And this happens only rarely.
> > > Some details below
> > >
> > > Any suggestions except will be appreciated.
> > > Thanks
> > > Old tony
> > >
> > > Some details.
> > > This has worked fine for 6 months.
> > > There are about 5000 memo according to the blobfix count Memo is
> > > called by using @KeyN
> > > @KeyN::':
> > > :: memo 157 edit("3","1","14","80") nowrap:
> > > Using SCO 5.06 and filepro 5.013
> > >
>
No, this is not the case. When you finish an @key, an implicit WRITE is
performed. I have not run into any situaions where data is not saved which
is entered during an @key. The situation I'm referring to is that if you do
a MEMO xx EDIT from an @key and immediately after do a MM X SHOW, you will
not see what you added. If you have a WRITE in between you will. This is/was
a bug with MEMO, it didn't have to do with the @key I don't think.

I'm pretty ocmfortable with @keys in general, haven't seen them lose any
data yet, and I don't use any explicit WRITE's.

Now, on the other hand, if you press F for Print Form, and that form has
some processing that updates field on that record... I have seen the need
for a WRITE under these circumstances. This, too, may have changed in the
recent past, but as of 20 years ago, which was the last time I tested
this... you *needed* a WRITE.