Still unable to split off the old years transaction from the gnucash file using jGnucashEditor-bin-2.0.26

[Colin Law]

On 26 April 2012 10:42, Vivek Agrawal <vickymnit at gmail.com> wrote:
> Colin, please don't consider it as I am forcing any point but wanted to
> share my viewpoint over here. :)
> As asked by you, the benefit over here is that over the period of time
> splitting the file on a particular date is beneficial for the financial
> organizations/individuals. As mentioned in my earlier mail, the financial
> year closing helps to save those files in untouchable state. It is like
> keeping those year transactions in the safe so that no one can access those
> transactions without permission.

Just make a copy of the file at the end of the year and archive that,
there is no need to remove the old data from the working file.

Colin

> I hope I have cleared my viewpoint. Also, this is just a suggestion for
> improving the tool but if it is very difficult to implement or it seems to
> be a low priority then it can be deferred. :)
>
> Regards,
> Vivek Agrawal
>
>
>
> On Thu, Apr 26, 2012 at 1:28 PM, Colin Law <clanlaw at googlemail.com> wrote:
>>
>> On 26 April 2012 08:53, Vivek Agrawal <vickymnit at gmail.com> wrote:
>> > Colin, Yes you are right at that point.
>> > But the point I am making here, is that what is the benefit of loading
>> > the
>> > file of larger size when you do not require the content of whole at the
>> > same
>> > point of time. The optimal way is to load only that part which requires
>> > changes. This part can be selected by user.
>> > In another way, we can think it as, some organizations generally keep
>> > the
>> > last 1 or 5 or 10 financial year transactions (depending on their
>> > business
>> > requirement). The previous transactions (i.e. before 1 or 5 or 10 years)
>> > are
>> > saved in archived. This also enables them to keep the earlier records
>> > safe
>> > and untouchable. Also, if required those files can be opened separately
>> > to
>> > make sure those transactions are still accessible. So, I was thinking if
>> > this could be implemented in some way in GnuCash also.
>>
>> What is the benefit of not loading the whole file, apart from a few
>> seconds when loading/saving?
>> Eventually I believe it is planned that when using the database format
>> rather than the xml version it will only load data as it needs it, so
>> then the fact that the old data is still there will not matter at all.
>>
>> Colin
>>
>> >
>> >
>> > Regards,
>> > Vivek Agrawal
>> >
>> >
>> >
>> > On Thu, Apr 26, 2012 at 12:59 PM, Colin Law <clanlaw at googlemail.com>
>> > wrote:
>> >>
>> >> On 26 April 2012 05:29, Vivek Agrawal <vickymnit at gmail.com> wrote:
>> >> > Thanks for the reply.
>> >> > So do we have similar option in GNUcash only i.e. functionality of
>> >> > splitting off the old years transactions from the gnucash file?
>> >> > I'm asking this because the file is growing in size and I have to
>> >> > keep
>> >> > the
>> >> > whole file while the old transactions are irrelevant for me.
>> >>
>> >> Usually this is not an issue as over the years the power of your PC
>> >> will increase much quicker than the size of the file.
>> >> For example in the years that I have been using gnucash the file has
>> >> grown to a couple of Megabytes whilst my hard disk has grown from 10GB
>> >> to 400GB and my PC has quadrupled in speed.
>> >>
>> >> Colin L.
>> >
>> >
>
>