Simplicty and flexibility!


LE9 build 6755 - multiview error: derivation in field is recurrent


Started by Sam Bird
Search
You will need to Sign In to be able to add or comment on the forum!

LE9 build 6755 - multiview error: derivation in field is recurrent

Apologies for repost - the related product was not entered on original post and post was not allowing replies

After latest LE9 6755 update the following error message appears when opening a form that has always worked before on LE9 without this error.

"multiview error: derivation formula for the field 'Repeat2' is recurrent is recurrent'

It also gives the same error for DQL insert /update using procedures that have been fine in the past.

Repeat2 is a virtual field which counts previous entries for the same "AR_Barcode" value in the same table.

if(AR_Barcode not = blank and Repeat2 = blank , count of "rSub_Submissions" + 1, 0 )

AR_Barcode is not the unique key for the table.

'rSub_Submissions' relationship is for the AR_Barcode field in the Submissions table vs the AR_Barcode field in the Submissions table

The error popping up on any form view of the table was solved by editing the table owning form.

Removed derivations in 'Repeat2' and related fields, saved form.

Re-entered same derivations and re-saved form.

No error on opening viewing forms. -- This implies the error is not with the field derivation

This though does not solve the error from occurring for DQL insert/update which then also causes a crash.

How can this be fixed without removing the field derivation?


Written by Sam Bird 10/09/24 at 07:04:09 LegEasy 9 Developer

Re:LE9 build 6755 - multiview error: derivation in field is recurrent

There is nothing done in 6755 that has anything to do with this or in many, many previous versions. 

In migrated code there can be many Easter eggs like this that simply has to be ironed out, and the longer the leap the more problems one will encounter.

DataEase is a complex product and applications made in it can be very complex on top of that. Moving forward will inevitably cause some problems that need to be ironed out by the developer. We don't have to time to investigate or fix problems like this on behalf of the developer, and only if it is as systemic problem will we investigate.

Part of a migration will always be re-development and to be honest it should be a much bigger part than a lot of people think as just moving old code forward does not take advantage of any of the improvements, possibilities or enhancements new versions allow.


Written by DataEase 10/09/24 at 10:23:20 LegEasy 9 Developer
DG3_ForumList