pcsoft.us.windevCopyright 2026, PC SOFT1 Nov 2019 07:57:44 Z31 Oct 2019 16:44:56 ZThere is probably a very easy way around this, but I cannot find it. I have set up a server trigger on a table which is activated after a new record is added or changed. That works fine and the trigger runs perfectly. All I need to do now is find out which record activated the trigger. Is there a command avaialbve which can return the record number of the table? Any suggestions are welcome. Thanks Simon30WEBDEVen_UShttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/67360-identifying-record-caused-trigger/read.awpmoderateur@pcsoft.fr (El moderador)webmaster@pcsoft.fr (El webmaster)gpredlpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/67360-identifying-record-caused-trigger-67369/read.awp1 Nov 2019 07:57:44 ZHi, of course, the automatic identifier is calculated & inserted while writing the record to disk. So, before writing it is not …https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/67360-identifying-record-caused-trigger-67369/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/67360-identifying-record-caused-trigger-67369/read.awpIdentifying the record the caused a triggersdbxoxpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/67360-identifying-record-caused-trigger-67368/read.awp31 Oct 2019 23:35:56 ZOk, got it. It was because I was using the HSave in the Add trigger code. All I have now done is changed the fields as I need …https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/67360-identifying-record-caused-trigger-67368/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/67360-identifying-record-caused-trigger-67368/read.awpIdentifying the record the caused a triggersdbxoxpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/67360-identifying-record-caused-trigger-67367/read.awp31 Oct 2019 23:22:21 ZOk, I have got round this by removing the Add Tigger and simply calling the Stored procedure from the client using HExecuteProce…https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/67360-identifying-record-caused-trigger-67367/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/67360-identifying-record-caused-trigger-67367/read.awpIdentifying the record the caused a triggersdbxoxpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/67360-identifying-record-caused-trigger-67364/read.awp31 Oct 2019 17:19:29 ZThanks for your quick reply Guenter. I suspected that would be the case, however, in the trigger code, I wrote a small amount…https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/67360-identifying-record-caused-trigger-67364/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/67360-identifying-record-caused-trigger-67364/read.awpIdentifying the record the caused a triggergpredlpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/67360-identifying-record-caused-trigger-67361/read.awp31 Oct 2019 16:56:32 ZHi, within the trigger code the whole buffer to be written is availabe!https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/67360-identifying-record-caused-trigger-67361/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/67360-identifying-record-caused-trigger-67361/read.awpIdentifying the record the caused a trigger