New record trigger

[Richard Kreiss]

> -----Original Message-----
> From: Kenneth Brody [mailto:kenbrody at spamcop.net]
> Sent: Friday, March 20, 2015 11:52 AM
> To: Richard Kreiss
> Cc: 'FilePro Mailing List'
> Subject: Re: New record trigger
> 
> On 3/20/2015 10:28 AM, Richard Kreiss wrote:
> >> -----Original Message-----
> >> From: Kenneth Brody [mailto:kenbrody at spamcop.net]
> [...]
> >>> As I recall, once a record is saved, @cd should equal @td and not be
> >>> empty.
> >>
> >> You recall partially incorrectly.
> >>
> >> Yes, once the record is "saved", @cd will be filled in.  But, when
> >> creating a new record input processing is done before the record is
> >> actually "saved". Therefore, @CD is still blank.
> [...]
> > I was referring to when the user (Windows) presses F10 or reaches a
> > "SAVE" in processing.
> >
> > Is not the record written at that point and the processing moved to
> > the top of the table?
> 
> No.  When you press SAVE, input processing runs/continues.  The record is not
> written/created until you execute a WRITE, or input processing ends.
> 
> Consider, for example, the case where input processing verifies the data, and
> refuses to save the record with invalid data.  Or where input processing brings
> up additional screens which need to be filled in before the record can be saved.

OK, tested this and have one question,  When the record is "saved" and the ending processing is completed, processing usually ends in and <end>.  At this point, the record is saved and filepro ends and exits the processing table.  Would there be a way to capture the exit code?  Or if one has systemed out to this add record process, what would be the exit code passed back the using qq=system() by just using an <end>?

Richard