|
OMG, that whole "Assume" analogy is so 70's. I think the biggest problem is with programmers that think their database design takes the place of good coding. Referential constraints are meant to be a last line of defense in database maintenance. They don't take the place of good program code. -----Original Message----- From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx] Sent: Wednesday, October 06, 2004 10:56 AM To: Midrange Systems Technical Discussion Subject: Re: Write statement Is that the ONLY condition that will cause it? I don't think so. What other conditions may cause such an error? - File full - Duplicate key - error on the trigger program associated with the file - referential constraint error. I think the biggest problem we have in getting developers to start using triggers, constraints and basically coming out of the 70's with their database design is a fear that they will have to bring their coding out of the 70's also. Goes back to the basic lesson: Assume can be broken down into three words A$$/u/me, or, you make an a$$ out of u and me when you assume. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com MWalter@xxxxxxxxxxxxxxx Sent by: midrange-l-bounces@xxxxxxxxxxxx 10/06/2004 10:45 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Fax to Subject Re: Write statement Duplicate Key on an Unique file. Thanks, Mark Mark D. Walter Senior Programmer/Analyst CCX, Inc. mwalter@xxxxxxxxxx http://www.ccxinc.com "Dwayne Allison" <Dwayne.Allison@aaga To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> i.com> cc: Sent by: Subject: Write statement midrange-l-bounces@m idrange.com 10/06/2004 11:42 AM Please respond to Midrange Systems Technical Discussion Hello All, What condition will cause '50' to equal '1'? Operation Factor 2 LO WRITE ARREC 50 -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. NOTE: This electronic message and attachment(s), if any, contains information which is intended solely for the designated recipient(s). Unauthorized disclosure, copying, distribution, or other use of the contents of this message or attachment(s), in whole or in part, is prohibited without the express authorization of the sender of this message.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.