Second attempt at submitting this one, may be there twice now.

We have three tables with a similar symbolic field which has a relational index which writes their record ids to different MVed fields in records of a fourth table which in turn has a btree index on part of its key for quick reference.

Sometimes entries are missed from these indexes, should this method be reliable or is there known problems with this sort of structure?

Goto www.sprezzatura.com and look at S/ENL Volume 2, Issue 7. Check the code for AddIndexTransaction. I believe this is what you will need to do as part of a Pre- or Post-Process Save Row subroutine.

HTH

Bill

Be aware that indexes are only checked for updating at the time the relevant record is written back. If the symbolic value changes after that time, the change will not be recognised and any subsequent change to the value indexed will not be picked up. For instance, if the date rolls over and causes the result of the symbolic to be 'expired' when yesterday it was 'unexpired', this change will not be picked up. This sort of problem may not be the reason for your non-update of symbolic index values but it is something that could be considered.

There's a 'depends on' attribute in the dictionary items for situations like this. Search the Sprezzatura Revmedia index for more information.

Yep, got the code, works like a dream!

Thanks Bill and others.

Actually isnt this code missing NewValue from TransactionRow.

And the first SaveRec should be SaveRecord.

I guess updating the "0" record updates both Btrees and Relational indexes - I will test them both. Pretty sure this is still the answer though.

Mea culpa - yes SaveRec should be SaveRecord or vice versa. In honesty push and pop session should have been used there - it was a quick and dirty.

And finally - please test thoroughly on relationals, we tend not to use them so….

The Sprezzatura Group

World Leaders in all things RevSoft

View this thread on the forum...