* Betr.: " Re: [tryton-dev] Statement Import" (Thu, 25 Oct 2012 12:04:03 +0200):
> If this is really what can happen (not in Belgium (knonw for its banks
> :-) because you can not retreive twice the same statement) than there
> is a problem in the workflow. You must have a way to retrieve statements
> that were not yet retreived otherwise there is no way to ensure
> correctness.
Just answering to this point only because I am lacking the time to take part in
the whole discussion:
You don't use banking programs in Belgium? AFAIK each serious banking software
has the ability to export statements belonging to random periods. It is
absolutely necessary to have a reliable mechanism to detect duplicates resp.
the correct sequence, if import files should overlap. The same way you must
recognize, if there is a gap between imports.
> In Tryton, we must force users to use the right way and not trying the
> correct it afterwards.
Welcome in the real world. You should be aware, that it is very often not
possible to determine 'one only right way' to meet the requirements of
different countries and purposes. I think I also remember your attitude 'the
fewest constraints as possible in a generic application'...;), which fits much
better in this subject.
--
Mathias Behrle
MBSolutions
Gilgenmatten 10 A
D-79114 Freiburg
Tel: +49(761)471023
Fax: +49(761)4770816
http://m9s.biz
UStIdNr: DE 142009020
PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6
signature.asc
Description: PGP signature
