Many thanks for you investigation and effort. Got you email and reviewing.

I am convinced it has something to do with the Detail Listing FWIW. I can replicate the file locking of the GLNUMB*.* files on my end and only when I exit Ledger do they get "released". Unfortunately I can not replicate the data corruption. Not sure who posted from Support yesterday but you could on your end replicate that the GLNUMB*.* files do not lock in V9.3A but do in V9.3B.

Regarding your analysis if the user printed the detail listing 10 minutes prior to 1028 being posted and did not exit the Ledger system my assumption is the GLNUMB*.* files are at that point locked and the issue appears. But why did other accounts post OK? That is the maddening part of this.

I am hoping R & D can find something at least correct the issue of the file locking on those files.

So as a pain in the you know what as it might be for the time being before they post anything in Ledger will have:

1. All users will communicate with each other and exit out of Ledger.
2. One user will go back in and check data integrity.
3. User will backup the Ledger data.
3. User will post the batch.
4. User will re-run data integrity to make sure all OK.
5. User will backup Ledger data again.

Thanks in advance for any further investigation and posts on this issue.