Thank you for this, Mark. I appreciate that arrays have no intrinsic key order, but it kinda seems intuitive that a 'split tValues by row' followed by 'combine tValues by row' should resolve to the original data. Knowing that the result of the first mangles the key order clarifies why it doesn't. I would, nevertheless, expect automatically allocated numeric keys to be numerically ordered.
I have set #8582 to not-a-bug. /H Mark Schonewille wrote Hugh, From your report, I can't conclude that his is a bug. Arrays have no order. Op 30 jan 2010, om 13:10 heeft Hugh Senior het volgende geschreven: > > http://quality.runrev.com/qacenter/show_bug.cgi?id=8582 > > split tValues by row, then > combine tValues by row > > The above should re-instate the original data, BUT... > > When combining values that have been split by row, the keys are > combined > alphabetically not numerically. This results in the data becoming > mis-ordered. > > Tip: Do not rely on split/combine to reproduce your original data! > > /H _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
