S
Sue Dilworth
I have deployed a macro to my user community which they
used to run in Word 97, but now are increasingly using
2000. If the Word 97 user processes a set of data then
there is no problem, the same data fails for the 2000 user.
The problem is occuring in documents sized approximately
230K. They contain around 25 tables each of 3 coulmns,
which the macro pastes into the Word document from EXCEL.
Early tables process OK, but at about table 18 or 21,
which are typically the largest in the document and tend
to break across 2 pages, then the cells become
misalligned, with typically entire subsequent rows in the
second half of the table being aligned half centimetre or
so the the left of the previous rows. The macro
processing, which requires a consistently configured
table, then fails. This table corruption is not
consistent. If the macro is re-run, then sometimes the
same table will fail but in a different place, sometimes
it will be the next table that fails.
I have written some error trapping into the macro. If this
manages to work round the problem, then all subsequnt
smaller tables will be formatted OK.
I see Microsoft acknowledges slow tables processing by
keyboard entry. Would this problem carry throug to VBA ?
Is there any way I can retrive the situation apart from
trapping the error, ignoring the corrupt table, and moving
processing onto the next portion of the document?
used to run in Word 97, but now are increasingly using
2000. If the Word 97 user processes a set of data then
there is no problem, the same data fails for the 2000 user.
The problem is occuring in documents sized approximately
230K. They contain around 25 tables each of 3 coulmns,
which the macro pastes into the Word document from EXCEL.
Early tables process OK, but at about table 18 or 21,
which are typically the largest in the document and tend
to break across 2 pages, then the cells become
misalligned, with typically entire subsequent rows in the
second half of the table being aligned half centimetre or
so the the left of the previous rows. The macro
processing, which requires a consistently configured
table, then fails. This table corruption is not
consistent. If the macro is re-run, then sometimes the
same table will fail but in a different place, sometimes
it will be the next table that fails.
I have written some error trapping into the macro. If this
manages to work round the problem, then all subsequnt
smaller tables will be formatted OK.
I see Microsoft acknowledges slow tables processing by
keyboard entry. Would this problem carry throug to VBA ?
Is there any way I can retrive the situation apart from
trapping the error, ignoring the corrupt table, and moving
processing onto the next portion of the document?