jsbeddow

New Members
  • Posts

    2
  • Joined

  • Last visited

jsbeddow's Achievements

New User

New User (1/3)

  1. Bradley, Sadly, I have come to the same conclusions as you: there seems to be no consistant reason or noticable behaviour on the part of keepass that would lead to this. I have also checked to see if any filestamp time changes (on the keepass file) after simply opening it and performing a search, but as far as I can tell, it does not rewrite the timestamp. There are, however, some options within keepass (android) that might bear investigating: under "Settings", "Application", then "File Handling", perhaps someone might be able to determine if the "Database caching", "Check for modifications", or "File transactions" settings have any effect on this. Keep us all posted...thanks.
  2. I can confirm that I have seen this exact same behaviour when sycning keypass files between Windows computers running 1.4.103 and Android mobile version 1.4.63: the older file versions on the Andriod frequently get "updated" onto the Windows machines, when I know that the newer version infactc exists on the Windows machine, resulting in lost data in the keepass files. This is manually repairable by resorting to backups in the archive folder (or elsewhere) but a real pain to keep track of. Please clarify the above info about minor changes on Android (mtime???) : does this mean that the android file system will always automatically "refresh/update" the file date/time stamp after simply opening a file, even without making any "real" changes to it? This would explain this disastrous behaviour. Perhaps keepass does this when simply performing a search on the database (it might consider this an update of where in the database to open to, upon next opening). Any workarounds?