Very interesting info. Gene - thanks for that Tidbit - as I stand corrected!
-K- -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Gene Wirchenko Sent: Monday, February 25, 2013 12:24 PM At 13:03 2013-02-22, "Kurt" <[email protected]> wrote: >Well - I guess you slashed One Phantom off your List! :-) > >As for a Corrupt EXE - I doubt it. How could it be corrupt - such that the >system Works - but, adds strange records. I suspect a truly corrupt EXE >would just Crash or Not work at all! I think the culprit is elsewhere... Very simple. It could be corrupt with the system working except it adds strange records. The point of something being corrupt is that you do not know what it does. There was a bug something like this in dBASE III Plus. You could join a collection of compiled programs into one file. When you did this, if you exceeded some limit, a bad file would be silently generated. The file would appear to run fine. The problem was that some of the code did not appear in the file, and when such code was called, it would be treated as if that code consisted of simply a return. [snip] Sincerely, Gene Wirchenko _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/38FBE36E308E4B0AB8157E28C8AA6D26@Programming2 ** 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.
