are you saying that a DB trigger does set some values in the row behind the back of servoy? This shouldn’t be done.
Yes, the trigger sets values into the createdby, createddate, updatedate and updatedby columns, IF these fields are inserted empty.
I need these triggers so that these fields get filled when records are inserted through other app/directly into the DB (Yes, i know they will not be seen by Servoy, untill Servoy’s cache is refreshed).
So, in the case where Servoy inserts values into these fields, nothing is done by the trigger.
Or are you saying that you have a modification auto enters attached in servoy to the columns but you don’t see those filled in when making a new record? That seems to be a bug.
No, I’m not saying that either. Servoy perfectly fills the values
What I am saying is the following:
I got a form in tableview. Alls the fields of the table are NOT editable.
Records get created just fine, the auto values createdate and create user name are filled just fine.
Then I start clicking away on the records, that are all NOT editable. all of a sudden, the modification user name field gets filled, allthough I didn’t update the records, since all fields are NOt editable.
When I then refrech the foundset (jumping to design vew and back), I see that the modificationdate and username fields have been filled. From the value they are filled with, I can see that they have been filled by the trigger.
and yes, I have checked if those field are not filled by the trigger on creation.
So, conclusion: clicking in non editable fields (at least in tableview) fires an update statement to the DB (which then offcourse triggers the trigger)
Paul[/quote]