We are noticing that UES (UEStudio '16 Windows 10 64-bit) may be locking files when they are opened.
When we open a file on a network share (J:\myfile.txt) and then on the server try to overwrite the file (e.g. with COPY) we get:
The process cannot access the file because it is being used by another process.
0 file(s) copied.
As soon as we close the file in UES the problem goes away. We are not technically "editing" the file - we have made no changes and are just viewing it.
When does UES decide to lock?
Is there any way to efficiently manage this? I.e. late locking?
When we open a file on a network share (J:\myfile.txt) and then on the server try to overwrite the file (e.g. with COPY) we get:
The process cannot access the file because it is being used by another process.
0 file(s) copied.
As soon as we close the file in UES the problem goes away. We are not technically "editing" the file - we have made no changes and are just viewing it.
When does UES decide to lock?
Is there any way to efficiently manage this? I.e. late locking?