Now I remember why I put the Read Events in a Custom APP object, instead of the form. The "Clear Events" needs to be placed in the Exit button.click and the form.queryunload event.
When the "Read Events" is in a different object "Clear Events" is only needed in one place. Form.unload Probably what was happening, each time you rebuilt the EXE, it was in use, and VFP wasn't telling you it was in use, so the EXE never got rebuilt. Your development environment has SET SAFETY OFF, I believe is the culprit that does it. After a restart, you should be fine, or finding and killing all instances in the Windows Task Manager - Processes tab Little things get us all the time, Tracy -----Original Message----- From: MB Software Solutions General Account Sent: Tuesday, May 12, 2009 5:10 PM Tracy Pearson wrote: > The only other two things that come to mind are > > LockScreen > Width/Height I've zipped the entire source. If you have a few minutes to have a look and test on your end, I'd appreciate it. It's just 18 KB: http://mbsoftwaresolutions.com/downloads/errorgrab.zip _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/000301c9d3cf$f2758990$d7609c...@com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
