Annoying Upgrade Bug - Database Too New
I have Realm Works on my desktop and my laptop. So every time I upgrade, I upgrade one install at a time. So when I next logon to the other machine, I get this message:
Quote:
So then I have to remember to go find the Realm Works Download page. It would be a small improvement to put a reminder and the link with this error message. |
Never had that issue, but for those who do, simply adding a link to the error message seems like a quick way to improve things.
+1 |
Don't know if this would work for sure, but you could try upgrading one machine, but don't sync the database. Then try to upgrade the other machine. Finally sync the database after all your machines have the latest version, preferably from your computer you last did any editing on.
|
If I understand your problem correctly, on the main startup screen when you get that message, you should be able to go to "Tools" on the top right beside "Realms" and then click the "Check for Updates" button which will download and install the latest version of RW.
|
Quote:
|
Which makes sense; until it opens the database it doesn't know the name of the Realm Works user.
Here's my question: how are you getting a newer database on a machine with an older version of the application? Are you copying your master.realm file around? |
Quote:
|
That's what I'd assume. My thought was that is that if you have to copy a giant data file and you know you need a newer version of the application to use it, copy the installer as well.
I agree with the suggestion that RW offer to go get it for you, though. Just that it's natural for me to bring installers along or go update the software myself when I know it works this way. Maybe I'm just old and used to programs that don't auto-update. :) |
Quote:
|
Oh. Well, then you have the easy workaround: don't log in. Just switch to the Tools tab and download the latest version. After installing that, then log in. :)
I thought it was giving you that message before reaching the Launcher. It would be clearer if it said something about the database on the server being a newer version than the local one, but I suppose it makes more sense in context as you're getting it right after logging in. It would still be a good change if it offered to do the update routine when you get that error. (Also if it offered to continue without being online.) |
All times are GMT -8. The time now is 04:02 AM. |
Powered by vBulletin® - Copyright ©2000 - 2024, vBulletin Solutions, Inc.
wolflair.com copyright ©1998-2016 Lone Wolf Development, Inc. View our Privacy Policy here.