Is it at all possible to delete a part with transactions tied to it?  All of a sudden, a part we've had for ages has suddenly "disappeared".  While balancing the inventory our accounting folks noticed a discrepancy and tracked it to the part.
 
Is the only way you can delete a part through IN-B?  Is there any way to see who may have deleted the part?
 
Is this possibly a bug?
 
Just checking all possibilities...
 
Any help/advise would be appreciated!
 
Thanks,
 
Val

In fact, this is nearly the same situation as my posting  "Duplicate Part #..?" from Jun 14th, 2007, 10:50am.
 
What the hey?  
 
Thankfully, if we didn't run inventory balancing reports daily we'd not have picked up on this little issue in one of our companies.  The other company is much more complicated and this would actually be a tough issue to discover.....
 
As to the part we mentioned today (me and Nancyc), the part existed yesterday, just fine, as it showed up on that day's reports.  This morning, bam! it's gone and these mystery parts are in its place, both having the same part # but different descriptions (one of the descriptions is the description for the now missing part).  
 
Something's amiss here....
 
Val

To continue the saga....Valerie did reindex those files earlier this month.  It didn't do any good.  
 
So, today, I decided to add back the missing part in inventory.  When I did, the transactions suddenly appeared in the history.  It was as if the part never went missing!!!!!
 
(I did have to recalc inventory book value to get the value into the record) The other two "ghost" parts are still in the inventory records.
 
I think we have more of a problem---we need to know why this is happening. Does this issue today help to understand what the problem is?
 

Well, I'm pretty sure it isn't a network card issue.  First thing every morning, and again in the afternoon,
I do system-wide checks.  My network utils designed to alert me of these sorts of problems don't scream
at me, and my manual checks of all the logs, etc. verify that the utils are truthful--no problems with nics, network communications, pc to network communications.  No one's dropping off the network.  Our accounting dept. does daily balancing, so they see whether something is a few cents or a few dollars or more off pretty much as it happens, they're that proactive in managing the numbers here.  Which may be more than what the average does.  So I don't know what else to say, except that this has just recently become a problem, and we need to determine what the cause is.
 
Guess we're on our own on this one......

I have not seen any of these problems.  I am running my inventory without warehouse control and with a single blank location.  Val, are you using multiple locations and/or warehouse control/bins?  If you are, maybe the problem is in one or both of these areas.  
If you are only using the single blank location, when you look at the location file in MDB (BKICLOC.BXX) do  you only have one blank location? (I have seen an error here in the past but not since the last few updates)
 
I don't think  you are on your own quite yet....

We only use the one location, and yes we do use warehouse control.  I can certainly check the location file to be sure there's nothing amiss in that...good idea worth trying.
 
There are no other issues with any other application run from the server, all the application error logs are clean. The only thing we keep seeing since the last update is this warning rollback messages in the Pervasive log for sales order files (T6soa...b files).  Lynn said that would be cleaned up in a later update. Other than that, we've been clean and continue to be clean on all logs, activity and error logs.
 
Val