@liebana It is good to see that the Spanish accounting is working due to the effort put into the localization. But the problem here is that the Spanish localization contains functionality that should be into the core! For example the Year End procedure into the localization fixes general issues that should be into the core, but contains also specific Spanish futures. Only the last should be into a localization. Then the profit/loss reports, these should be into the core but are into the localization. By the way, Year End procedure into the core has had a important fix. Is the localized version still working now? https://bugs.launchpad.net/openobject-addons/+bug/531507
Result is that every localization is generating it's own (duplicated) code with their bugs). This is not a DRY (Do not Repeat Yourself) approach. For me accounting is the hart of an ERP-system. Almost every action will have associated cost with that action, that could/should be input into the system. The problem we face is that even basic accounting has it's limit's now and we shouldn't try to solve this into localizations. That should only contain country specific modifications/adds. ------------------------ Jan www.veritos.nl www.supportandmaintenance.org -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=59405#59405 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
