pcsoft.us.windevCopyright 2026, PC SOFT2 Dec 2015 10:42:00 Z2 Dec 2015 07:11:00 ZHi I love these new internal procedures but I have just come across some undocumented behaviour which might save someone else some time. In a nutshell don't try using RESULT in an internal procedure. I call a procedure from a button. This procedure returns true or false. Within that 'parent' procedure I have an internal procedure which also returns true or false. The code RESULT InternalProcedure seems to work correctly in the debugger but the button always gets False returned to it. I then declared a variable in the 'parent' procedure, changed my code to MyVar=InternalProcedure Result MyVar with exactly the same result. The odd thing is according to the debugger MyVar gets set to the correct value but the result returned to the button is always negative. The only way I can get it to work is to forget about using RESULT in the internal proc & just directly set the value of MyVar to true or false within the internal proc. Cheers David30WEBDEVen_UShttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/55239-wd20-internal-procedure-quirk/read.awpmoderateur@pcsoft.fr (El moderador)webmaster@pcsoft.fr (El webmaster)guestpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/55239-wd20-internal-procedure-quirk-55245/read.awp2 Dec 2015 10:42:00 ZQuote David Egan Hi I love these new internal procedures but I have just come across some undocumented behaviour which …https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/55239-wd20-internal-procedure-quirk-55245/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/55239-wd20-internal-procedure-quirk-55245/read.awp[WD20] Internal Procedure Quirk