× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: record with duplicate key
  • From: D.BALE@xxxxxxxxxxxxx
  • Date: Wed, 10 Jan 2001 18:08:00 -0500

Bypass?  You mean, be able to still write a duplicate key that the UNIQUE
keyword guards against.  Nope.  You'll have to remove the UNIQUE keywords from
the affected DDS to "bypass" the error.

Well, before you go trotting off removing the UNIQUE keywords from these
files, you should have an understanding as to *why* they were put there in the
first place.  If there's a legitimate reason why the UNIQUE keyword is
specified, i.e. you can never have a given customer number appear twice in the
Customer Master file, and, for example, that's why you got your "duplicate
key" error, then you need to fix the program that's getting the error.

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952

-------------------------- Original Message --------------------------
        Are you sure the LF you are using is causing the problem? Or should
I  ask: are
        there more LF's defined as UNIQUE?


Yes there are more LF's defined over the file. Is there a way I can bypass
those 'other' UNIQUE keys?

Adam
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.