As I'm in need to solve the problem for my customer, I have reflected on that topic as well. I'm just wondering how the big guys with their proprietary EPR solutions attack this problem.
Suppose that some entry in the business document is the result of a python function. Despite from the fact, that you end up accumulating a lot of garbage, would a duplicate set of SQL tables be useful in that case? Or how can one ensure that even the data structure always stays the same across several versions of Tiny? I think that most businesses don't even care about every single business transaction back in 2003 as long some key data for statics remains being accessible in addition to all the legal business documents. For the business document problem, the ".pdf plus meta-data" approach seems very reasonable. -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=31437#31437 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
