I have been told that copying information from Microsoft Excel into TRACE's component tree view can potentially cause errors by overriding hidden cells in TRACE. Has anyone else heard this? If so, is it true? Is there a workaround?
This came up after a project that utilized copying information from Microsoft Excel had problems with some of the library members becoming corrupt. I was told by a colleague that the issue could be from pasting values into TRACE. I believe the issue was actually in the archiving process, because I tend to see the problem when archiving the project on one computer and opening it on another.
No I have not heard of this. I've done it plenty of times without issues. What's hidden that's being changed?
Be Sustainable -- Never let today use up tomorrow!.
This is my stance on this issue as well.
This came up after a project that utilized copying information from Microsoft Excel had problems with some of the library members becoming corrupt. I was told by a colleague that the issue could be from pasting values into TRACE. I believe the issue was actually in the archiving process, because I tend to see the problem when archiving the project on one computer and opening it on another.
Weird. Can't say I'm suprised though.
Be Sustainable -- Never let today use up tomorrow!.