01-16-2018, 05:05 AM
It doesn't matter if the companion app knows what storage location is used on the device (it does know this already in fact). What matters is the location of the files specified in the database itself. If you just transfer the Android database file to Windows, every file path is going to be listed based on what was used on the Android device. Every one of those paths will be invalid on Windows. Using paths that are relative to the storage location (along with a flag which specifies whether the path is relative or absolute) should fix this problem for most users, but users who like to use a combination of folders, especially those outside the storage location parent folder, are still going to run into problems. I could certainly add a feature to the companion app that is similar to the "Fix Broken File Paths" option in the Android version so that you can replace paths in the database with a different path if desired, but that will only work well if you structure your files/folders in such a way that they all have the same base path (which is true if you let MobileSheets manage your files).
Mike
Mike