MEMO Question

guy_templin guy_templin at adelphikitchens.com
Thu Sep 6 19:50:07 PDT 2007


Did you check to see if @bd (batch update date) was updated?

Guy Templin
Adelphi Kitchens, Inc.

On Thu, 6 Sep 2007 21:53:26 -0400, John Esak wrote
> Hmmm,
> Your question brings up some interesting points. I did a quick test 
> of @key... since it brings you into update mode... I just naturally assumed
> that it would certainly change @ud. So I did:
> 
> 	then: end
> SkeyT  if:
> 	then: mesgbox @ub < @ud
> 	then: end
> 
> And oddly enough pressing the T key did *not* change the @ud to today's
> date.
> 
> I would have thought that it *should* change to today's date.
> 
> So, this implies that the SHOW MEMO function has an implicit WRITE built
> into it if your @ud is changing when you do that simple @key code.
> 
> There was a tiny bug... no more or less a gotcha... where the MEMO function
> did not immediately write it's changes to the memo field.... and I think
> they changed it to fix or at least modify this behavior?  So, if you 
> are testing on 5.6 maybe that change has given you this behavior 
> which you don't want.
> 
> All in all, and judging by the odd behavior of the @key *not* 
> writing the @ud date... I, at least, can't give you the seemingly 
> obvious answer that @key *always* updates the system maintained @ud 
> field...  And now, I have a question of my own.  Why not?  :-)
> 
> Since, we can't get past this one, it will be hard to get to the MEMO
> question... but I'm afraid the answer is going to be you *can't* 
> change how it works.
> 
> Actually, I don't really think that an @key *should* update the 
> system maintained fields... not unless the record is actually 
> updated. Heck, what if your @key just browses into another file.... 
> why should it update the SM fields on the current record?  It 
> shouldn't.  I was just making the assumption that by virtue of 
> entering "update" mode, this would trigger the write when that state 
> was left.... unless the state was "broken" out of.... I guess we 
> have to wait for clarification, on this, and the MEMO question.
> 
> 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 Doug Luurs
> > Sent: Thursday, September 06, 2007 9:42 AM
> > To: filepro-list at lists.celestial.com
> > Subject: MEMO Question
> >
> >
> >  Question for you all ...	(SCO 6 / fp 5.6)
> >
> >     When using the MEMO Command :-
> >
> > @Key7    If:
> > '##############################################################
> >        Then: '#    Switch to Notes Screen
> >          If:
> >
> >        Then: switchto  "7"
> >
> > 287  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
> > -
> >          If:
> >
> >        Then: memo 681 show("4","1","18","80")
> >
> > 288  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
> > -
> >          If:
> >
> >        Then: End
> >
> > This is Updating the @UD & @UB fields ?
> >
> > Or how would I program a switch to screen with a memo field and show the
> > memo without it
> > updating the @UD/@UB fields ?
> >
> > ________________________________
> >
> > Doug Luurs
> > Systems Programmer
> >
> > Borisch Manufacturing Corporation
> > 4511 East Paris SE
> > Grand Rapids, MI  49512-5314
> > Phone: (616) 554-9820 Ext 143
> > Fax:      (616) 554-9821
> >
> > --
> > These commodities/technical data are controlled under the United
> > States Export
> > Regulations and may not be exported to a foreign person, either
> > in the U.S. or
> > abroad, without the proper authorization of the U.S. Department
> > of State or the
> > U.S. Department of Commerce. Please contact Borisch Manufacturing
> > Corporation
> > for commodity classification and jurisdiction.
> >
> > This E-mail, including any attachments, may contain confidential
> > information and is intended solely for use by the individual to whom
> > it is addressed.  If you received this E-mail in error, please notify
> > the sender, do not disclose its contents to others, and delete it
> > from your system.  Any other use of this E-mail and/or attachments
> > is prohibited.  This message is not meant to constitute an electronic
> > signature or intent to contract electronically.
> >
> > _______________________________________________
> > 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



More information about the Filepro-list mailing list