we have a transaction that doesn't generate mv-fields but a single field with blank-seperated values like starttime="123 345 4565" instead of the expected starttime="123" starttime="345" starttime="4556".
If we reduce the number of events it works fine.
best regards Marco
thank you, this works, if I make a "makemv" after it for every field I need as mv-field. If it is possible, I want to know under which conditions the transaction-command stops to generate mv-fields. I think it a strange behaviour that transaction do it sometimes so and sometimes other...