Subject | Re: Desgin question - Mutiple years of data, single database or many? |
---|---|
Author | Bhavbhuti Nathwani |
Post date | 2009-08-17T17:58:42Z |
Thanks a lot Geoff you have explained everything I have faced in a very details manner. First of all it was a relief to know that what I was doing was not out of the world. As per your suggestion I am fine with summarizing the previous years data that is needed in the current years database reporting.
Now that you have been through this and have managed it, I would like to ask you about outstanding receivables. I have currently kept a flag field in the invoices tables which is set to true if an invoice belongs to the previous (or still older) year so that it will remain readonly and will not have any relevance in accounting except for bill-to-bill adjustments for debtors list and o/s letter purposes. These such o/s invoices are not removed in the end-of-year processing until they are either written-off or adjusted completely in the current year. Is this way of mine good in your views? Do you have any suggestions for this.
Thanks and regards.
Bhavbhuti
Now that you have been through this and have managed it, I would like to ask you about outstanding receivables. I have currently kept a flag field in the invoices tables which is set to true if an invoice belongs to the previous (or still older) year so that it will remain readonly and will not have any relevance in accounting except for bill-to-bill adjustments for debtors list and o/s letter purposes. These such o/s invoices are not removed in the end-of-year processing until they are either written-off or adjusted completely in the current year. Is this way of mine good in your views? Do you have any suggestions for this.
Thanks and regards.
Bhavbhuti
--- In firebird-support@yahoogroups.com, Geoff Worboys <geoff@...> wrote:
> Each problem domain can be, often subtly, different... and it
> will almost certainly change over time. With that disclaimer
> in mind:
> ...