can not save in 2016 and 2018

Hi

I'm using Ver 5.31(2011) generally
but I also sometimes use Ver 8.00(2016)
in my opinion, Ver 8.00 has fatal bug
after I saved with some changes( ex arrangement chages....) and then ran...I found the result is not for changes....it's for before change....
first time I knew it's my mistake..so I tried more then 4 times...
and found same result...
so I tried also with Ver 10.00(2018) which is the latest version...
same result...
result did not include chanages....C2 did not save changes...
but it's not always working.... sometimes it's working...
Please let me know why this situation is happened to me and how can I fix this error..

Thanks~

You give us little to work with here.
Is ANY change you make not recorded, sometimes?
We all are troubled by (what appears to be) illogical response from software but my assumption here is that there may be illogical expectations.
In what part of the program is this occurring? What are you trying to change?

Sometimes the compression process doesn't works => in the same directory you can have both "*.C 2" and *._A files.
Therefore you can't know which one caesar opens: the *.C 2 or the *._A???

=> go to Config / Miscellaneous options / Compress Caesar Files = FALSE

Other bugs due to *.C 2:
- lost of *.C2DB file (lines numbers)
- impossible to import load cases from a compressed file *.C 2

1) With regards to the compression activity - make sure none of the files are "read only".

2) The line number in ".c2db" are not addressed by the neutral file conversion.

3) If you need to import load cases from other jobs, turn off compression.

Also in my organization, we have seen that the compression routine often fails with large files, especially if they are placed in a shared folder.
It seems that CaesarII software (at now we use the last 2018 version and updates) can't wait more that a precise time, after that, it creates *._A files without compress or partially compressions.

wishing that the new version 2019 of CII solves this issue.
thanx

We are looking at the compression library. We hope to improve this in v.11 (2019).