Hi Peeter, On Fri, Jan 11, 2019 at 4:05 PM Peeter Pärtel <peeter@sigma.ee> wrote: still on 1.2.26 as it is the last version where I can freely change all

existing invoices. As mistakes happen or clients want some other description etc changes on them, this is really important to us.

Yes, you brought up that point before, I remember. Actually, you were not the only one to bring it up -- I've got a few other contacts that would really like this functionality to be re-introduced again. Some time back, I went over the possibilities to do so with Chris and we found a way to extend LedgerSMB 1.3+ to support both your use-case and still maintain Chris's position about not deleting data (maintaining a full audit trail). Unfortunately, the pipeline for 1.7 is very full at the moment and I'm not likely to be able to address this idea and build it into 1.7 (as that release is planned for this summer). But as latest version of Debian where 1.2.26 works is Debian 8 and it's end

of life is June 30th 2020 we are planning to move away from LedgerSMB to some other software. Already migrating some companies starting 2019 and rest is planned starting from 2020.

It's not that I'd like to encourage you to keep working on 1.2, but if you want to keep working on 1.2, I think that version can be made to work on Debian 9+ quite easily.

If there has been any changes in allowing to change existing invoices (both parts and services), then it would be good to know before we have left completely.

Yes, there has been a change in allowing existing invoices to be changed in the sense that the project now has a way to maintain full audit trail, working COGS *and* allow the changed invoices. Which means we're no longer against allowing it. The actual code to allow it though is yet to be written. Thanks for taking the time to respond! Regards, Erik.

Your point about the manual is fair. However, 1.4, 1.5 and 1.6 are actually not too different from 1.3. There are differences, especially with respect to how the UI is built and there are some more functions in later releases, but there really shouldn't be anything removed. <<thank you for knowing this and there we can adjust to the new versions promptly. Yes, you can migrate to higher versions than 1.3 and retain your data. If you're interested in how to do that, I'll create a separate write-up about it. As to whether the migration itself or the use of the new version is completely without issues, I'm not sure. Especially the step to migrate from one minor version to another (1.4->1.5->1.6) has been improving with each release. The reason I was asking the question - and thanks for your answer - is because I wanted to know if there are users who are in need of migration from 1.2/1.3->1.6+. And you confirm that there are. <<I am interested to the migration of 1.3 going to 1.4 or higher version available.Hoping to get your write-up the soonest. Warm Regards.:) Ryle.Msinc/ITDept From: Erik Huelsmann <ehuels@gmail.com> To: users@lists.ledgersmb.org Cc: Ryle Zabate <ryle_23@ymail.com> Sent: Saturday, January 12, 2019 7:46 AM Subject: Re: Are there any subscribers using LedgerSMB versions older than 1.4? Hi Ryle, Your mails aren't appearing in my inbox, so I'm pasting your response below:

Hi, thank you for your question. On our case, we are still using the 1.3.46 release since the only available pdf manual is only for 1.3  version. Your point about the manual is fair. However, 1.4, 1.5 and 1.6 are actually not too different from 1.3. There are differences, especially with respect to how the UI is built and there are some more functions in later releases, but there really shouldn't be anything removed.

Can we now migrate to higher versions of LSMB without any issues and retaining the data of the 1.3 setup? Yes, you can migrate to higher versions than 1.3 and retain your data. If you're interested in how to do that, I'll create a separate write-up about it. As to whether the migration itself or the use of the new version is completely without issues, I'm not sure. Especially the step to migrate from one minor version to another (1.4->1.5->1.6) has been improving with each release. The reason I was asking the question - and thanks for your answer - is because I wanted to know if there are users who are in need of migration from 1.2/1.3->1.6+. And you confirm that there are.

Regards, Erik. On Tue, Jan 1, 2019 at 3:41 PM Erik Huelsmann <ehuels@gmail.com> wrote: Hi all, Migrations have become considerably more controlled since the 1.5 release, which introduces a smooth migration from 1.4. As such migration paths do not exist for 1.1, 1.2 and 1.3, I'm eager to learn if there are any users out there of these old versions, and, if you're not migratiing, what's keeping you from doing so. If you can't publicly respond to this inquiry, please mail me privately so I can treat your information confidentially. Thanks for your responses, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP.Robust and Flexible. No vendor lock-in. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP.Robust and Flexible. No vendor lock-in.