pcsoft.us.windevCopyright 2026, PC SOFT12 Oct 2016 07:13:00 Z6 Oct 2016 20:56:00 ZHello All Over the last year I have noticed that code that previously worked fine sometimes stops working and I couldn't work out now until today. The examples are very specific and are restricted to code in one window that references variables in a prior window. e.g. I set a global variable in the current window to false, open another window and in that window I reset the variable in the first window by direct reference as window1.variable = true The normal reason for doing this is that something I do in the second window requires the first window to redisplay or recalculate some data. Yesterday a client lodged a support call for code running in this manner that was working fine and now throws an error 1020. The code works fine in my environment, both code and development. Previous examples of this type of failure include cases where the variable in the calling window just did not accept the value assigned to them in another window or just crashed. This time I had an inspiration and checked the patches I had sent to the client and the first window had been patched so I sent the client a patch that contained both windows and that fixed the problem. My conclusion is that the compiler incorporates other window calls in a way that causes problems if one window changes. I have used this coding methodology for many years and I can't recall it being an issue so maybe something has changed in the compiler process in V20 This is a big problem if you code in the manner that I do with other window references as I will now have to test for calls to other windows before issuing a patch. Regards Al30WEBDEVen_UShttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59844-wd20-previously-working-code-doesn-any-more/read.awpmoderateur@pcsoft.fr (El moderador)webmaster@pcsoft.fr (El webmaster)guestpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59844-wd20-previously-working-code-doesn-any-more-59931/read.awp12 Oct 2016 07:13:00 ZHi Yogi, in case 1 thought of that already - no joy. Case 2 has been solved, it really has been the data, not the program.https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59844-wd20-previously-working-code-doesn-any-more-59931/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59844-wd20-previously-working-code-doesn-any-more-59931/read.awp[WD20] previously working code doesn't any moreguestpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59844-wd20-previously-working-code-doesn-any-more-59929/read.awp12 Oct 2016 06:42:00 ZHello Al and Guenter, In both these cases ask your clients to stop/pause/disable their antivirus application and then run you…https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59844-wd20-previously-working-code-doesn-any-more-59929/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59844-wd20-previously-working-code-doesn-any-more-59929/read.awp[WD20] previously working code doesn't any moreguestpcsoft.us.windevhttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59844-wd20-previously-working-code-doesn-any-more-59849/read.awp7 Oct 2016 07:49:00 ZHi Al, yes, with WD21 I'm experiencing strange things too and cannot locate any reasons. Previously, a compiled WD program used …https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59844-wd20-previously-working-code-doesn-any-more-59849/read.awphttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/59844-wd20-previously-working-code-doesn-any-more-59849/read.awp[WD20] previously working code doesn't any more