Here is the primary file trigger list: TRIGGER definitions for file LOANS at 15:00:17 07 MAR 2019 PAGE 1
TYPE...... AMEND. TERM.. DEBUG. SUBROUTINE NAME............... prewrite YES NO NO JBASE.CALLX.LOANS.BP predelete YES NO NO JBASE.CALLX.LOANS.BP 2 Records Listed There are NO triggers on the secondary file. On Thursday, March 7, 2019 at 2:40:45 PM UTC-8, Tom J wrote: > > We are using jBASE 5.6 on Linux Centos 7.6. We recently experienced a > system freeze forcing a console stop, then boot. A file was damaged beyond > repair as a result of this system freeze and had to be restored from a > prior backup. All indexes on this file were deleted. We also removed the > file]I. The indexes were then recreated. > > We have a primary file with a trigger that updates this (secondary) file. > Some of the attributes on this secondary file are indexed. Prior to the > system freeze the indexes on the secondary file would update properly after > the trigger on the primary file updated the secondary file attributes. > > After the system freeze this does NOT happen. Updating an indexed field > on the secondary file automatically correctly updates the corresponding > index. Updating the secondary file with the primary file trigger does > update the secondary file properly but the corresponding index on the > secondary file is NOT updated. > > How do we get the indexes updating automatically after the primary file > trigger updates the secondary file? > > Any advice and suggestions are greatly appreciated. TIA. > -- -- IMPORTANT: T24/Globus posts are no longer accepted on this forum. To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en --- You received this message because you are subscribed to the Google Groups "jBASE" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
