I'm not claiming that my code is error free. I'm trying to reach a state where I'll be able to handle errors in the conventional fashion without c++ buffer overruns. The field validation rule just tests to see that the value supplied is greater than zero. It has to be there becase going forward, other apps than mine will be writing to this table. I agree that, in the short term, where I control the code and the data the rule shouldn't be necessary.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Derek Kalweit Sent: Thursday, February 08, 2007 4:20 PM To: [EMAIL PROTECTED] Subject: Re: More buffer overrun: 2 specific cases > This *may* have been a case of copying a table back & forth without > including the index. Other than that, I'm not sure. It's only happened > once or twice. What does your field validation rule do? If it's unattended, why do you have it as a field validation rule instead of simply validating in regular code itself? Oh, and copying around a table without the index is obviously just asking for trouble.... -- Derek [excessive quoting removed by server] _______________________________________________ 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 ** 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.
