RE: JBA ML - "WARNING: Item has previously been deleted."

The warning good the first pass through, not each time you access the
record.

-----Original Message-----
From: jbausers-l-admin@midrange.com
[mailto:jbausers-l-admin@midrange.com]On Behalf Of
Jeff_Klipa/Harvard@harvardind.com
Sent: Wednesday, October 24, 2001 11:38 AM
To: jbausers-l@midrange.com
Subject: RE: JBA ML - "WARNING: Item has previously been deleted."


I think the Warning is a good thing...
The INP34 record (sales Analysis Deleted records file) triggers the
warning...
If you're going to reuse a deleted part # then I think a warning is a good
idea...

Yeah, we deleted any INP35F records that had no match in INP35 and that
solves
the problem...

We had to rewrite the entire Delete Routine to cover Manufacturing stuff as
well, so we'll simply add the INP35F file to that too...

Thanks.







"Diana Larsson" <dlarsson@ardencompanies.com> on 10/24/2001 11:33:46 AM

Please respond to jbausers-l@midrange.com



  To:          jbausers-l@midrange.com

  cc:          (bcc: Jeff Klipa/Harvard)



  Subject      RE: JBA ML - "WARNING: Item has previously
  :            been deleted."







Jeff,
We just ran into the same situation. We chose to clear inp35f when we do the
deletions and that took care of our problem. It lets us re-add the item but
the message "WARNING: Item has
previously been deleted." always comes up. I am working on that piece as we
speak.
Diana


-----Original Message-----
From: jbausers-l-admin@midrange.com
[mailto:jbausers-l-admin@midrange.com]On Behalf Of
Jeff_Klipa/Harvard@harvardind.com
Sent: Wednesday, October 24, 2001 10:55 AM
To: jbausers-l@midrange.com
Subject: JBA ML - "WARNING: Item has previously been deleted."


Program IN002 - Menu 2/INM - When attempting to re-add items to INP35 that
have
been previously deleted you receive this warning message "WARNING: Item has
previously been deleted."  The user is required to press the reset key.  If
the
user attempts to proceed past the warning the program fails and produces a
program dump.

Here's a snippet of that dump:
Program Name . . . . . . . . . . . . . :   OSLINP3/IN002
 Last File Used . . . . . . . . . . . . :   INP35F1P
 Last File Status . . . . . . . . . . . :   01021
                  attempts to write duplicate record (C G S D F).

Further more, an incomplete INP35 record is created thereby populating INP35
with corrupt data.
(The only way for us to then clean up the mess is to delete the corrupt
INP35
record, the INP35F record must be deleted manually as well.)

During the Item deletion routine 26/INU (which leaves a great deal to be
desired
in terms of completeness) INP35F in particular is not purged of the deleted
item
records.

Does anyone else have any experience with or insights into this problem...?

Thank you.


_______________________________________________
This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
To post a message email: JBAUSERS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/jbausers-l
or email: JBAUSERS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/jbausers-l.


_______________________________________________
This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
To post a message email: JBAUSERS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/jbausers-l
or email: JBAUSERS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/jbausers-l.




_______________________________________________
This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
To post a message email: JBAUSERS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/jbausers-l
or email: JBAUSERS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/jbausers-l.