06-22-2015 09:14 AM
You are probably right about the reason for the crash. Still, the Bottom Line is that Embedding an Excel Table does not cause a crash, even with a "too-wide" Table, and (while I don't, obviously, have an accurate timing due to the crash) Embedding seems several-fold faster.
Reports are something the User wants to create and see. If the User asks for too much so as to be unreadable, he or she can simply say "Well, maybe instead of 20 columns, I'll choose these 12". However, it is much less helpful/useful if there is no report to examine/modify due to a crash.
There may well be a Good Reason to ultimately embed a selected Text Table of the proper size in Word directly. I'm guessing (but obviously haven't checked) that an Embedded Excel Table and an Embedded Word Text Table will have similarities in formatting, so one might be able to test How Much To Put In The Table using Excel (which is fast and doesn't crash), then recode a sufficiently-small subset as a Text Table in Word (small enough to avoid crashes and to have acceptable Font Size, never mind how slow it takes).
Bob Schor
06-23-2015 08:47 AM
Guys,
i just worked with word table.Thanks for your suggestions and good covversion as well.
Now I need some help on formatting cell of the word table.
In below pic (same as above),under time stamp column the time stamp value in each cell going to second and third line,which i need to make to come to single line and other channels data cell, better for me to be as it looks now.
Please assist on this.
06-23-2015 11:01 AM
How about helping us to help you? Post your code -- we can then "play" with it and do our own "experiments" to attempt to solve your problem.
Bob Schor