difference in behaviour of onRecordInsert event 3.5.9 <-> 4.

Hi,

noticed some strange difference between 3.5.9 and 4.1.1.

We have forms with a lot of fields, so we split them up in several tabforms.
The baseform is empty and contains all the tabforms with the fields.
The baseform and the tabforms are all based on the same


The relation is the same for alle tabforms
.pk to
.pk.
There is also an onRecordInsert event on this

The onRecordInsert event is triggered when a saveData is done after a newrecord.

This worked fine in 3.5.9

In 4.1.1 the onRecordInsert event is triggered at the moment you do a newRecord.
So it is fired without a savaData.

I remembered a remark from Johan Compagner about selfjoined relations in 4.x.
This is a relation with only tablenames, but no columnsnames.

I changed the relation and the issue was gone.

BUT the onRecordInsert event is also triggered when you do a
forms..elements..readOnly=true;
on a tabform that is in any tab but the first.
It seems this last problem only occurs the first time after solution startup.

When done on the first tabform it is no issue.

Just wanted to share this in case anyone runs into this.
Took me a lot of time to find out what the problem was.

I will also create a case for this one. (case 204878)

Hi,

Tested this in latest intermediate build and issues are solved there !!!

Regards,

Hans