Jump to content

Michael K.

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Michael K.

  • Rank
    Casual Member
  1. Now I realised what 'Display plain text' does, I had to switch back off because I need the formatting. I don't run Nvivo on a network but the file is stored in a Dropbox folder for added backing up. If that complicates things, I can keep the master .nvp file in a non-Dropbox folder and create copies on Dropbox. I do appreciate that autosaving huge files may not be a good idea, but some sort of incremental autosaving may be efficient enough. At the moment, reminders are just annoying and switching them off is asking for trouble, particularly when the setup is not very reliable. For now, I just hit Ctrl+S every few minutes and I will keep my setup hoping Nvivo won't crash. So far, so good. Incidentally, given the potentially sensitive nature of the data, encrypting the .nvp file on-the-fly, particularly when it is stored on the cloud, will be great. I know we can use third-party encryption for that.
  2. Nvivo 64-bit crashed several times here and after the event I realised I hadn't seen any autosave pop-ups for hours, so I just lost work as a result. I wasn't doing anything particularly demanding when the crashes occurred, and autosave has always been set to 15 minutes. I am attaching the crashinfo file here. I must say I was fuming when I realised what happened and I have much less confidence in the stability of the product now. Quite simply, we can't afford crashes in the middle of big volumes of analysis. Whatever error happens, the application must be able to handle it. I just switched on 'Display plain text...' as recommended and hope for the best. crashinfo_374aefc3-0b13-48dd-8034-1083f3d56a2c.log
  • Create New...