The Android version has not kept pace with the desktop version due to lack of developers able/willing to support it.
Cannot open from Dropbox
Moderator: Renato
-
- Developer
- Posts: 1535
- Joined: Sat Dec 06, 2008 2:27 pm
- Are you a spam bot?: No
- Location: Sankt-Petersburg, Russia
Re: Cannot open from Dropbox
-
- Senior User
- Posts: 21
- Joined: Fri Sep 27, 2019 2:25 pm
- Are you a spam bot?: No
Re: Cannot open from Dropbox
Hy,
any news about this post and about the post "syncro Dropbox problems?
I have been using MMEX for more than 2 years now and I had chosen it because similar to MS Money 2000, but also because it had an ANDROID version that promised well.
But actually I have NEVER used the ANDROID versions that sometimes I installed, sometime for synchronization problems and others time because they did not open the .mmb file on Dropbox at all.
In the end and for a long time I've been used only the WINDOWS client.
Now I can't understand if everything is still stopped at this post dated 2020 or if (maybe !!) there are any positive news.
ps:
I currently have my file.mmb (not encrypted) on DROPBOX, I WORK WITHOUT PROBLEMS from Windows with the latest version.
On Android I have tha android app version 2019.02.28.997 (but is it the latest?).
Via android app I can open the file and work with it, I use both the folloing kethod:
- run the app and open my file as "last open file" known to the app,
- setting tha file in Drpbox app and executing the command "open with ... ".
My problem is I don't understand how a catch often occurs between Dropbox's standalone sync and the Android app's SYNCR command.
Indeed:
A - if I do not execute the SYNC command, when I reopen from Windows I DO NOT find the new transactions entered via the Android app (and this seems correct to me, because only the file on the smartphone has been updated and not the remote one on Dropbox);
B - if I run it, I receive a successful update message from the app, but then:
-- my file opened by WINDOWS as "last opened" does NOT contain my last updates;
-- the system creates a file "myfile(username's.conflicted copy).mmb" and THIS FILE CONTAINS UPDATES (?? !!)
- Then I MUST perform two renames, first of the file.mmb in "fileold.mmb" and then of the above file "conflicted" in file.mmb
But then the SYNC command of the android app should be used or not?
maybe the command must to be used only when allocating the myfile.mmb on others clouds as Google Drive or One Drive?
Finally, I remember correctly or not that during the installation phase you had to set the link to the remote file on Dropbox?
I don't know anymore and I can't find the parameter of the android app that I have iposted, maybe you choose it only during the installation phase from apk and then I have to re-install?
Thank you
---
any news about this post and about the post "syncro Dropbox problems?
I have been using MMEX for more than 2 years now and I had chosen it because similar to MS Money 2000, but also because it had an ANDROID version that promised well.
But actually I have NEVER used the ANDROID versions that sometimes I installed, sometime for synchronization problems and others time because they did not open the .mmb file on Dropbox at all.
In the end and for a long time I've been used only the WINDOWS client.
Now I can't understand if everything is still stopped at this post dated 2020 or if (maybe !!) there are any positive news.
ps:
I currently have my file.mmb (not encrypted) on DROPBOX, I WORK WITHOUT PROBLEMS from Windows with the latest version.
On Android I have tha android app version 2019.02.28.997 (but is it the latest?).
Via android app I can open the file and work with it, I use both the folloing kethod:
- run the app and open my file as "last open file" known to the app,
- setting tha file in Drpbox app and executing the command "open with ... ".
My problem is I don't understand how a catch often occurs between Dropbox's standalone sync and the Android app's SYNCR command.
Indeed:
A - if I do not execute the SYNC command, when I reopen from Windows I DO NOT find the new transactions entered via the Android app (and this seems correct to me, because only the file on the smartphone has been updated and not the remote one on Dropbox);
B - if I run it, I receive a successful update message from the app, but then:
-- my file opened by WINDOWS as "last opened" does NOT contain my last updates;
-- the system creates a file "myfile(username's.conflicted copy).mmb" and THIS FILE CONTAINS UPDATES (?? !!)
- Then I MUST perform two renames, first of the file.mmb in "fileold.mmb" and then of the above file "conflicted" in file.mmb
But then the SYNC command of the android app should be used or not?
maybe the command must to be used only when allocating the myfile.mmb on others clouds as Google Drive or One Drive?
Finally, I remember correctly or not that during the installation phase you had to set the link to the remote file on Dropbox?
I don't know anymore and I can't find the parameter of the android app that I have iposted, maybe you choose it only during the installation phase from apk and then I have to re-install?
Thank you
---