Suppose a table contains baan a text field, and that we should share the table between the company 100 (which contains the physical table) and 101 (which contains the table instead of logic). Suppose also that the texts are not shared.
In this case, the way it has baan handle the text shows smarter than expected, although not completely satisfactory.
fact, if the text field is not set (that contains the value zero), if I open the editor to create a session, the text will be created in the company always 100, regardless of whether I open it by 100 or 101: This means that, in the presence of shared tables, the text is always open in company that hosts the physical table.
Problems arise, however, once the subject is valued: in fact, as is well known, it contains a number that refers to the table but the texts.
If, for example, on the 101, I try to make a copy of the record, the control is referential to the record copy to fail because the text has been created on the 100, and the system generates an error of reference. There is a
did a little 'curious, at least for BaanERP level solution that had the system I was working on: the 101, the system allows, in any case and without generating errors, to modify the original record, provided not going to change the field text itself and modify than other fields.
But I reserve to make more checks before confirming this fact publicly, because this behavior is quite unique and I wish it was not due to lack REORGANIZE tables.
0 comments:
Post a Comment