ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Items >> Duplicate Part #..?
http://www.istechforum.com/YaBB.pl?num=1181832634

Message started by gtladmin on 06/14/07 at 07:50:34

Title: Duplicate Part #..?
Post by gtladmin on 06/14/07 at 07:50:34

Here's a weird one. We have had in the system a part, mr6eg-188, type f. Someone (we'd love to be able to audit this stuff some time!) has entered a second mr6eg-188, type N. You can see both in IN-A. When you select the first part, the correct info comes up on the screen. If you select the 2nd part, initially it shows the info for the 2nd part but after a few seconds the info switches to the that from the 1st part. (Are you following me?).

We're pretty sure there's no history to this part per inventory transactions, but when you do an inv trans report it shows the original part w/ transactions, and then the duplicate part with the same transactions. Running a Crystal report shows only the original part with it's transactions, nothing else.

Can we just delete this part somehow? I'm going to try to just reindex the table to see what happens.

Val

Title: Re: Duplicate Part #..?
Post by gtladmin on 06/14/07 at 08:00:08

Ok, reindexing didn't work, for either the BKICMSTR or MTICMSTR

Title: Re: Duplicate Part #..?
Post by gtladmin on 06/14/07 at 08:02:46

oops...didn't mean to enter that quite yet....sorry

The part actually showed up only in BKICMSTR, not MTICMSTR. Interesting...So there was nothing tied to the part at all, so we did just go into MDB and delete that part. Real mystery as to how it happened, which would be solved if we could audit this stuff to see which goofy user made the mistake and re-train them so it does not happen again. :-)

Val

Title: Re: Duplicate Part #..?
Post by kkmfg on 06/14/07 at 12:54:35

Just so long as the "retraining" doesn't involve a rubber hose! ;-)

Title: Re: Duplicate Part #..?
Post by gtladmin on 06/14/07 at 13:12:14

Oh no, we would NEVER use a plain old rubber hose! We have experts here that go more for the velvet hammer..... ;)

Seriously, I am an advocate for bringing the mistake to the user's attention and working with them to determine why it happened and how to avoid the mistake in the future. There's no blame, just awareness and learning from those mistakes so we don't have repeats.