The normal practice any production build, is to have "off" to range checking, I/O and Overflow.
These are in essence debug type options. Range check will always at some stage cause issues with mouse operations. Part of the issue is that Delphi's range checking is flawed (or well was last time I looked - it reported range check errors on loading of negative integers in some cases). Overflow could be left on, but I can't say I have checked the generated code to ensure it will not suffer the same issues as range checking. Another way to say this is that I have yet to suffer from a Overflow check failure in using Delphi for 6/7 years. Myles. -----Original Message----- From: Mark Howard [mailto:[EMAIL PROTECTED] Sent: Thursday, 11 December 2003 10:32 To: [EMAIL PROTECTED] Subject: [DUG] Another debugging question In my D7 Compiling options I have Runtime Errors Range, I/O and Overflow checking all turned ON. One site has reported a "Range Check Error" when running my application, on all their workstations. I cannot duplicate the problem on either of my developmemnt machines. Seems I have 2 options: Turn Range checking off in the compiler or track down the problem. Can anyone advise how to track down where the error is occurring since it doesn't give any address and I can't duplicate it here? TIA Mark _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi
