> Can some one please point me to some documentation as to contents of a
> trigger buffer.

The best place for this would be the archives, just search for trigger and
you should get plenty of samples.  http://archive.midrange.com

> I know I can add a physical file trigger, can the trigger be
> on a field specific?

No. The trigger is on a record.  Was a record Added, Changed or Deleted.
That's what fires a trigger program.

> Can I know which field/fields changed without comparing the before and
> after images?

That's how you do it, comparing the before and after images.  But it is
not that difficult at all.  You create two external Data descriptions based
on the file the trigger is for.  Then point one at your before image and
one at your after image (use prefix on the data structure) then you would
just do something like:

C          If     BF_MyVar <> AF_MyVar
         do something...

A month ago I could of given you some examples, but I'm no longer at the
company where I wrote trigger programs and haven't gotten any here yet.

The archives should have some excellent samples though.

Regards,

Jim Langston
Programmer/Analyst
Cels Enterprises, Inc.

-----Original Message-----
From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On
Behalf Of Giri Gopal
Sent: Tuesday, August 28, 2001 10:13 AM
To: rpg400-l@midrange.com
Subject: Trigger Files

Hi:

Can some one please point me to some documentation as to contents of a
trigger buffer. I know I can add a physical file trigger, can the trigger be
on a field specific? or Can I know which field/fields changed without
comparing the before and after images?


Thanks for your help in advance.
GG



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.