That’s not necessarily true, see Geert’s discussion of Bayesian
import-matching. There are some other feature blocks but they require overt
user action to use a new feature. The block is easily worked around by making
a separate backup of your data file before trying GnuCash 3.x., though you
w
I found it odd to get stuck on an earlier version without testing a new one
before.
I use GnuCash 3.3 on W10 without major issues, except for what development
has not yet given us and the critical version migration issues have already
been resolved and I've helped in this.
Bug reporting is one way
Paul,
A warning, once your data file has been touched by a version 3 Gnucash it
cannot be opened by versions before 2.6.21.
Use a test file for practice.
David C
On Sun, Nov 25, 2018, 11:31 AM Geert Janssens Paul,
>
> No, but it's easy to up-or downgrade the installed version. You can just
> r
In retrospect it may be interesting to add a bit more detail to my train of
thought. I skipped it in my original mail as David is a long-time user so I
took some parts for granted.
Installing a different version of gnucash can introduce issues on several
levels:
Firstly, format changes in how
Paul,
No, but it's easy to up-or downgrade the installed version. You can just run
the installer of the version you want and it will replace the one currently
installed.
The ability to install two versions side by side is something I am interested
in setting up though.
Regards,
Geert
Op zon
Geert:
Is it possible to install two versions, side-by-side, in Windows?
Thanks
Paul
On Sun, Nov 25, 2018 at 7:56 AM Geert Janssens
wrote:
> David,
>
> You keep saying this. While I respect your choice to stay on the safe
> side,
> the only way to know if gnucash 3.x works for you is to test it
David,
You keep saying this. While I respect your choice to stay on the safe side,
the only way to know if gnucash 3.x works for you is to test it. That's pretty
easy in Windows.
So I encourage you to run a few tests on a backup of your data file and
evaluate how good or bad that works out. I'
Paul,
You are not the only one that concerned about whether the new releases meet
your needs any better than what you used before. A bird in hand is
better...
I am staying with my favorite 2.6.15 or 2.6.17 until I am satisfied that
3.4 or whatever is sufficiently well debugged to not present any
I have files that contain many years of transactions [<2 MB]. Last year was
done with 2.6.12 which I think provides accurate numbers. Starting a new
computer on Windows 10, I would like to transition to 3.3 and stay current.
When I open an old file and run a balance sheet I get some very strange
r
