Path: csiph.com!1.us.feeder.erje.net!feeder.erje.net!1.eu.feeder.erje.net!ecngs!feeder2.ecngs.de!81.171.118.63.MISMATCH!peer03.fr7!futter-mich.highwinds-media.com!news.highwinds-media.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Wolfgang Riedmann" Newsgroups: comp.lang.clipper.visual-objects Subject: Re: Altd() stops program in production exe Date: Tue, 4 Apr 2017 16:37:41 +0200 Lines: 28 Message-ID: References: X-Trace: individual.net oS6KRfrb9qdAcdof5f8kNQtPeArAeiNlm/7yiSh25PsJ7Y/6U= Cancel-Lock: sha1:Zg9PK9KAxEMm7DqJfmOiqGO2ES8= User-Agent: XanaNews/1.18.1.6 X-Received-Bytes: 1368 X-Received-Body-CRC: 784362336 Xref: csiph.com comp.lang.clipper.visual-objects:10375 Hi Dick, from all PCs my software runs on there is only one that has this issue. Strangely enough, it is occurring even with debug set to off. Since then, before delivering an exe, I do a global search on AltD(). Wolfgang D.J.W. van Kooten wrote: > I have a weird thing with 1 client. There's a certain loop the program > runs and it stopped halfway. But not in my program, with the same > data. After a while I realized that this was exactly at an Altd() > breakpoint. > > I did have Debug still on on their exe, but how it is possible that an > exe is stopping at Altd()? I've only seen it there; it happens > occassionaly that a mef has the debug status on in production, and > more than once that an Altd() is still "active". > > Dick --