Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #10892
| From | Martin <Martin@spam.spam> |
|---|---|
| Newsgroups | comp.lang.clipper.visual-objects |
| Subject | Re: XP & 7, perfect W10 not responding |
| Date | 2017-08-18 16:12 +0100 |
| Organization | A noiseless patient Spider |
| Message-ID | <on6vt2$bav$1@dont-email.me> (permalink) |
| References | <ola7p0$3ga$1@dont-email.me> <on6gqg$r19$1@dont-email.me> <4qldpc1sd2vg2973c79m1k8a5b9usairv5@4ax.com> |
One day one crash due to a missing field (older data newest .exe) So looks OK Thanks for these ideas as well. On 18/08/2017 13:06, D.J.W. van Kooten wrote: > Replying on message of Fri, 18 Aug 2017 11:55:11 +0100 from Martin: > > > Hello Martin, > >> We MAY have found the issue >> Compiler options >> All were set to High Optimisations >> Changed some to none, Right SLE, bBrowser, Reportpro >> and now it SEEMS OK. > > Strange...On 24-8-2004 I started a thread > Compiler "checks" : what's wrong with this one? > > With enable Operator Methods, this gave a runtime error and without it > didn't: > > !(Empty(nTray) .OR. nTray=NIL .OR. nTray=0) > > Although one of the conclusions was to use Isnil instead, it was > clearly compiler settings dependent. > > However, Robert wrote: > > "Optimisation to High/Speed does nothing. It is a relict from VO 1" > > He also wrote: > > Less checks means faster code, but also more risks. For example more > risks for 5333s or apps hanging because overflow errors are not > detected. > > > Dick >
Back to comp.lang.clipper.visual-objects | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
XP & 7, perfect W10 not responding Martin <Martin@spam.spam> - 2017-07-26 15:12 +0100
Re: XP & 7, perfect W10 not responding Martin <Martin@spam.spam> - 2017-07-26 15:14 +0100
Re: XP & 7, perfect W10 not responding Frans Wauters <info@wautersit.com> - 2017-07-26 10:49 -0700
Re: XP & 7, perfect W10 not responding Martin <Martin@spam.spam> - 2017-08-01 13:38 +0100
Re: XP & 7, perfect W10 not responding D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2017-08-02 11:06 +0200
Re: XP & 7, perfect W10 not responding D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2017-07-27 00:16 +0200
Re: XP & 7, perfect W10 not responding Martin <Martin@spam.spam> - 2017-08-02 10:42 +0100
Re: XP & 7, perfect W10 not responding D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2017-08-04 01:33 +0200
Re: XP & 7, perfect W10 not responding Martin <Martin@spam.spam> - 2017-08-04 12:13 +0100
Re: XP & 7, perfect W10 not responding dlzc <dlzc1@cox.net> - 2017-08-04 07:14 -0700
Re: XP & 7, perfect W10 not responding Martin <Martin@spam.spam> - 2017-08-07 09:02 +0100
Re: XP & 7, perfect W10 not responding dlzc <dlzc1@cox.net> - 2017-08-07 07:06 -0700
Re: XP & 7, perfect W10 not responding Martin <Martin@spam.spam> - 2017-08-09 16:20 +0100
Re: XP & 7, perfect W10 not responding Martin <Martin@spam.spam> - 2017-08-09 17:00 +0100
Re: XP & 7, perfect W10 not responding Martin <Martin@spam.spam> - 2017-08-18 11:55 +0100
Re: XP & 7, perfect W10 not responding D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2017-08-18 14:06 +0200
Re: XP & 7, perfect W10 not responding Martin <Martin@spam.spam> - 2017-08-18 16:12 +0100
Re: XP & 7, perfect W10 not responding "Heiko J. Pongratz" <heiko.pongratz@ctsedv.de> - 2017-08-18 15:40 +0200
Re: XP & 7, perfect W10 not responding Martin <Martin@spam.spam> - 2017-08-18 16:12 +0100
Re: XP & 7, perfect W10 not responding dlzc <dlzc1@cox.net> - 2017-08-18 07:17 -0700
Re: XP & 7, perfect W10 not responding Martin <Martin@spam.spam> - 2017-08-18 16:13 +0100
Re: XP & 7, perfect W10 not responding Martin <Martin@spam.spam> - 2017-09-19 10:26 +0100
csiph-web