pcsoft.us.windevCopyright 2026, PC SOFT17 Oct 2016 03:34:00 Z14 Oct 2016 00:54:00 ZHi I have just encountered a (so far) seemingly strange thing... I created a new project - and imported global procedures from an existing project. [WD19] (The existing project is a standard 64 bit configuration - the new project is configured as a webservice) The new (WD webservice project) gives compile errors for out of scope variables. The variables "are" out of scope in that they are declared within an IF-ELSE-END block - then used/referenced outside the block (below the declaration). However, this code does not flag any errors in the existing Windows project - and seemingly works fine. I am trying to figure out how and why the compiler works differently with different configurations. So far, I am just assuming that that is the way it is - and that as a 'webservice' it is being compiled with a different compiler - perhaps for compatibility with the application server? Anyone have any insights as to what is actually happening? Regards Derek30WEBDEVen_UShttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59964-variable-out-scope/read.awpmoderateur@pcsoft.fr (El moderador)webmaster@pcsoft.fr (El webmaster)guestpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59964-variable-out-scope-60011/read.awp17 Oct 2016 03:34:00 ZAh! Yes. Thank you!https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59964-variable-out-scope-60011/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59964-variable-out-scope-60011/read.awp[WD] variable out of scopeguestpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59964-variable-out-scope-59969/read.awp14 Oct 2016 09:46:00 ZHello ! See option in WinDev (Project -> Compilation -> Scope of local variables limited to the current block) [attachment…https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59964-variable-out-scope-59969/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59964-variable-out-scope-59969/read.awp[WD] variable out of scope