When going into IN-B Enter Inventory the system is crashing when saving an item whether it is changed or not. Our customer is on the latest version but has been experiencing this problem with previous versions as.   I am guessing it has something to do with their data but am not sure how to troubleshoot the error.
 
The error justs states that "An error has occurred in the application."
 
Trevor Abbott
Advanced ERP Limited NZ
V2020.2

You actually need to look for a ^01 extension, not a ~

Those File sizes seem to fine. Let me ask you this does this problem you describe happen on all workstations or just one? Did you run the Binary Zeroes fix utility and did you re-index those files? Do you get an error if so a screenshot would be nice, if you have the option to view the error and or print or save it do so. Also a screen shot of the IN-B program you are using might prove helpful.
 

I have completed the Fix Binary Zeroes and have re-indexed the Inventory files BKICMSTR, MTICMSTR and BKICLOC, the evoreindex file showed that there were a different number of transactions in the BKICMSTR and MTICMSTR.   I assumed that there were records in one and not the other, though both appeared to match.   The difference related to duplicates and in one instance a triplicate copy of one item in both BKICMSTR and MTICMSTR.   I have now cleared there extra entries though it hasn't made any difference on the inventory crashing.  This may have been contributing to other inventory related problems they have been experiencing.
 
I have compiled screenshots and error reports in an excel spreadsheet so will email a copy for your information.   Lastly there two files in excess of 2GB as Lynn suggests, as follows: -
 
ISMICADT - 2,885,156 KB
ISICADT - 2,097,144 KB
 
Though I can't see any evidence of the segmenting you mention.

Do you have ISMICADT.^01 in the folder? If you have anything with ^01 extension, that is the culprit.

When you open IN-B the ISTS Enhancement is at the top of the program.
Does the error occur immediately after the click on the Save button? If they try and do this directly on the server does the same error come up?
 

Ok - So I looked at the ISMICADT and the ISICADT files.   Opened one in Maintain database and discovered a large number of blank transactions at the beginning of the file.   Tried to run Fix Binary zeroes, though it was taking so long.   It was after running this that the ISICADT - (first one i started on) was reduced in size in the file directory and now also had another copy with - wait for it - a ^.01 extension.  I then tried to re-index the file with limited success and then tried the Pervasive rebuild utility, which the log file said was successful though I couldn't get to where it would finish.   I did do this on my test system so far.   As these two files are my culprits I will focus on getting these sorted.   I also tried to purge records though again was taking so long - to be expected with so many records and a file of that size.
 
I am wondering how useful are these files and can I shortcut and copy blank copies from the Default company?   From what I can see they don't provide a lot of detail as to what the transactions were?

Quote from TrevorA on 07/23/20 at 12:04:30:

 
I am trying to understand the difference between UT-C  reindex and the Pervasive Rebuild Utility.