Jump to content

Chris Darby

Level 1
  • Content Count

  • Joined

  • Last visited

Community Reputation

7 Neutral

About Chris Darby

Profile Information

  • Subscription
  1. I haven't tried this, but if you have an additional drive available, and then reinstall Evernote on that other drive, then I wonder if the database would also be stored on that other drive. If that doesn't work, then there might be some other tricks involving file path redirects or symbolic links to fool the Evernote application into accessing the database on another drive (i.e., maybe Evernote looks to store data in C:\Evernote\data\ but a redirection mechanism forces it to actually store on E:\Evernote\data\).
  2. There does not seem to be an offline database in the sense that the full collection of notes are available while offline. The new Evernote seems to only download a note when it is opened while online, after which point in time that particular note (that was previously opened) will then be available while offline. However, if I have thousands of notes and have not opened each one of them recently while online, then when I am offline on an airplane I am not able to open those other notes. Put another way: If I have recently opened notes 1 through 100 while online, then I can access those offline
  3. Thank you for sharing your experiences with this, I do greatly appreciate it.
  4. I keep running into this issue with technology and I suspect others do as well. We invest significant time and effort over years to make use of some incredible tools that people create, like Evernote, and we are more than happy to continue to purchase or subscribe to their services as a result, but then our "house of cards" teeter on the brink of collapse when the product suddenly and unexpectedly breaks or dissolves. As you alluded to, as we each organize and tag thousands of records, enabling us to rapidly retrieve past thoughts and concepts through indexed searches, leaves us dependent on t
  5. Exactly. The approach should have been to make the new version available, but not force everyone onto it. The current properly functional application should be maintained while they continue to improve the new-and-improved modern shared code base (etc. etc.) version separately. I understand where they're coming from, they want to simplify, reuse code, organize, modernize and try to future-proof their products, and where they're going with the new version is probably on the right path. However, to suddenly force (or at least mislead) everyone to upgrade (downgrade?) without warning, and to leav
  6. I agree as well. I was just looking to see if this issue has been mentioned and it looks as if I'm not alone.
  • Create New...