Thanks Support. I purposely haven't posted anything on this yet but it is to the point now something is going wrong at a client site.

They have continually been getting corrupted Ledger data for the past two weeks now and it appears (and I stress appears) that is a user generates the detail listing this locks the files. In the meantime another user posts a Ledger batch, or that same user that generated the listing posts a batch and they get corrupted data.

In theory if these files are locked (and I know this by going out to the DOS prompt and try to rename them I get the access denied message) then when you try to post these files can not get updated and hence corrupted data?

The other issue is these corruptions appear to have coincided with the Ledger V9.3B upgrade yet no other clients are having this issue to my knowledge with the upgrade applied.

We have rebooted the server and workstations thinking this might be part of the problem but it doesn't appear so.

I have attempted on my end rename the GLNUMB*.* files when I generate the Detail Listing and they are in fact locking. Yet when I post on my end integrity comes back clean.

Continuing to investigate but in my mind these files should not be locking.

Sorry a ramble.