Making 2 Tables into 1 Table

More stuff on tables... Will MS _ever_ get it right?

I've got 2 tables with a blank line in between them. (They were created
independly of each other, not by simply splitting one table into two.)
Normally, if you remove the blank line between 2 tables the tables become 1
automatically. However, sometimes (like this time) the tables stay as 2
tables, even though there's nothing between them - not even a continuous
section break. I really don't want to have to go through all the work of
recreating a single table as the 2 tables are both quite complex - lots of
varying column widths within groups of rows and styles and shading and
borders, etc.

Does anyone know of a way - either manually or through code - to force these
two tables to concatenate?

--
Cheers!
The Kiwi Koder
(37 sleeps and counting...)

Doug
Tue Dec 04 16:58:57 PST 2007

Add a new row at the end of the first table, then select the second table
and use Right Click Cut and then select the new row that you added to the
first table and the Right Click and use Paste Rows. Then delete the empty
row

--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP

"NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote in message
news:A5368E40-D7B9-4B74-A69D-D2866F8C8955@microsoft.com...
> More stuff on tables... Will MS _ever_ get it right?
>
> I've got 2 tables with a blank line in between them. (They were created
> independly of each other, not by simply splitting one table into two.)
> Normally, if you remove the blank line between 2 tables the tables become
> 1
> automatically. However, sometimes (like this time) the tables stay as 2
> tables, even though there's nothing between them - not even a continuous
> section break. I really don't want to have to go through all the work of
> recreating a single table as the 2 tables are both quite complex - lots of
> varying column widths within groups of rows and styles and shading and
> borders, etc.
>
> Does anyone know of a way - either manually or through code - to force
> these
> two tables to concatenate?
>
> --
> Cheers!
> The Kiwi Koder
> (37 sleeps and counting...)

gordon(dot)bentleymix(at)gmail(dot)com>
Tue Dec 04 17:47:01 PST 2007

A noble effort, Doug, but alas no joy. Now I have 3 separate tables: the
original 2 and a third with just a blank row in it below the second one. It's
not terribly important (yet) that it all be just one table, so I think I'll
just leave it for now. If it becomes critical I guess I'll have to rebuild
the table from scratch. :-(
--
Cheers!
The Kiwi Koder


"Doug Robbins - Word MVP" wrote:

> Add a new row at the end of the first table, then select the second table
> and use Right Click Cut and then select the new row that you added to the
> first table and the Right Click and use Paste Rows. Then delete the empty
> row
>
> --
> Hope this helps.
>
> Please reply to the newsgroup unless you wish to avail yourself of my
> services on a paid consulting basis.
>
> Doug Robbins - Word MVP
>
> "NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote in message
> news:A5368E40-D7B9-4B74-A69D-D2866F8C8955@microsoft.com...
> > More stuff on tables... Will MS _ever_ get it right?
> >
> > I've got 2 tables with a blank line in between them. (They were created
> > independly of each other, not by simply splitting one table into two.)
> > Normally, if you remove the blank line between 2 tables the tables become
> > 1
> > automatically. However, sometimes (like this time) the tables stay as 2
> > tables, even though there's nothing between them - not even a continuous
> > section break. I really don't want to have to go through all the work of
> > recreating a single table as the 2 tables are both quite complex - lots of
> > varying column widths within groups of rows and styles and shading and
> > borders, etc.
> >
> > Does anyone know of a way - either manually or through code - to force
> > these
> > two tables to concatenate?
> >
> > --
> > Cheers!
> > The Kiwi Koder
> > (37 sleeps and counting...)
>
>
>

Doug
Tue Dec 04 17:57:33 PST 2007

I'd be interested in seeing the document if you can share it.

--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP

"NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote in message
news:26330FE4-CF32-4520-A1D7-8368FB985609@microsoft.com...
>A noble effort, Doug, but alas no joy. Now I have 3 separate tables: the
> original 2 and a third with just a blank row in it below the second one.
> It's
> not terribly important (yet) that it all be just one table, so I think
> I'll
> just leave it for now. If it becomes critical I guess I'll have to rebuild
> the table from scratch. :-(
> --
> Cheers!
> The Kiwi Koder
>
>
> "Doug Robbins - Word MVP" wrote:
>
>> Add a new row at the end of the first table, then select the second table
>> and use Right Click Cut and then select the new row that you added to the
>> first table and the Right Click and use Paste Rows. Then delete the
>> empty
>> row
>>
>> --
>> Hope this helps.
>>
>> Please reply to the newsgroup unless you wish to avail yourself of my
>> services on a paid consulting basis.
>>
>> Doug Robbins - Word MVP
>>
>> "NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote in
>> message
>> news:A5368E40-D7B9-4B74-A69D-D2866F8C8955@microsoft.com...
>> > More stuff on tables... Will MS _ever_ get it right?
>> >
>> > I've got 2 tables with a blank line in between them. (They were created
>> > independly of each other, not by simply splitting one table into two.)
>> > Normally, if you remove the blank line between 2 tables the tables
>> > become
>> > 1
>> > automatically. However, sometimes (like this time) the tables stay as 2
>> > tables, even though there's nothing between them - not even a
>> > continuous
>> > section break. I really don't want to have to go through all the work
>> > of
>> > recreating a single table as the 2 tables are both quite complex - lots
>> > of
>> > varying column widths within groups of rows and styles and shading and
>> > borders, etc.
>> >
>> > Does anyone know of a way - either manually or through code - to force
>> > these
>> > two tables to concatenate?
>> >
>> > --
>> > Cheers!
>> > The Kiwi Koder
>> > (37 sleeps and counting...)
>>
>>
>>

gordon(dot)bentleymix(at)gmail(dot)com>
Tue Dec 04 18:53:00 PST 2007

I'll send you a 'sanitised' version - just the segment of the doc that
contains the 'Troublesome Tables'. It's part of a much larger template, but
I've confirmed that the problem still exists even when the tables in question
are removed from their natural environment.
--
Cheers!
The Kiwi Koder


"Doug Robbins - Word MVP" wrote:

> I'd be interested in seeing the document if you can share it.
>
> --
> Hope this helps.
>
> Please reply to the newsgroup unless you wish to avail yourself of my
> services on a paid consulting basis.
>
> Doug Robbins - Word MVP
>
> "NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote in message
> news:26330FE4-CF32-4520-A1D7-8368FB985609@microsoft.com...
> >A noble effort, Doug, but alas no joy. Now I have 3 separate tables: the
> > original 2 and a third with just a blank row in it below the second one.
> > It's
> > not terribly important (yet) that it all be just one table, so I think
> > I'll
> > just leave it for now. If it becomes critical I guess I'll have to rebuild
> > the table from scratch. :-(
> > --
> > Cheers!
> > The Kiwi Koder
> >
> >
> > "Doug Robbins - Word MVP" wrote:
> >
> >> Add a new row at the end of the first table, then select the second table
> >> and use Right Click Cut and then select the new row that you added to the
> >> first table and the Right Click and use Paste Rows. Then delete the
> >> empty
> >> row
> >>
> >> --
> >> Hope this helps.
> >>
> >> Please reply to the newsgroup unless you wish to avail yourself of my
> >> services on a paid consulting basis.
> >>
> >> Doug Robbins - Word MVP
> >>
> >> "NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote in
> >> message
> >> news:A5368E40-D7B9-4B74-A69D-D2866F8C8955@microsoft.com...
> >> > More stuff on tables... Will MS _ever_ get it right?
> >> >
> >> > I've got 2 tables with a blank line in between them. (They were created
> >> > independly of each other, not by simply splitting one table into two.)
> >> > Normally, if you remove the blank line between 2 tables the tables
> >> > become
> >> > 1
> >> > automatically. However, sometimes (like this time) the tables stay as 2
> >> > tables, even though there's nothing between them - not even a
> >> > continuous
> >> > section break. I really don't want to have to go through all the work
> >> > of
> >> > recreating a single table as the 2 tables are both quite complex - lots
> >> > of
> >> > varying column widths within groups of rows and styles and shading and
> >> > borders, etc.
> >> >
> >> > Does anyone know of a way - either manually or through code - to force
> >> > these
> >> > two tables to concatenate?
> >> >
> >> > --
> >> > Cheers!
> >> > The Kiwi Koder
> >> > (37 sleeps and counting...)
> >>
> >>
> >>
>
>
>

Doug
Tue Dec 04 21:12:34 PST 2007

The issue here was that one of the tables had the "Text wrapping" set to
"Around" and for the other, it was set to "None".

The setting must be the same to enable tables to be joined into one.

--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP

"NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote in message
news:364A6B0A-727F-41D6-BA21-E73803B74175@microsoft.com...
> I'll send you a 'sanitised' version - just the segment of the doc that
> contains the 'Troublesome Tables'. It's part of a much larger template,
> but
> I've confirmed that the problem still exists even when the tables in
> question
> are removed from their natural environment.
> --
> Cheers!
> The Kiwi Koder
>
>
> "Doug Robbins - Word MVP" wrote:
>
>> I'd be interested in seeing the document if you can share it.
>>
>> --
>> Hope this helps.
>>
>> Please reply to the newsgroup unless you wish to avail yourself of my
>> services on a paid consulting basis.
>>
>> Doug Robbins - Word MVP
>>
>> "NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote in
>> message
>> news:26330FE4-CF32-4520-A1D7-8368FB985609@microsoft.com...
>> >A noble effort, Doug, but alas no joy. Now I have 3 separate tables: the
>> > original 2 and a third with just a blank row in it below the second
>> > one.
>> > It's
>> > not terribly important (yet) that it all be just one table, so I think
>> > I'll
>> > just leave it for now. If it becomes critical I guess I'll have to
>> > rebuild
>> > the table from scratch. :-(
>> > --
>> > Cheers!
>> > The Kiwi Koder
>> >
>> >
>> > "Doug Robbins - Word MVP" wrote:
>> >
>> >> Add a new row at the end of the first table, then select the second
>> >> table
>> >> and use Right Click Cut and then select the new row that you added to
>> >> the
>> >> first table and the Right Click and use Paste Rows. Then delete the
>> >> empty
>> >> row
>> >>
>> >> --
>> >> Hope this helps.
>> >>
>> >> Please reply to the newsgroup unless you wish to avail yourself of my
>> >> services on a paid consulting basis.
>> >>
>> >> Doug Robbins - Word MVP
>> >>
>> >> "NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote in
>> >> message
>> >> news:A5368E40-D7B9-4B74-A69D-D2866F8C8955@microsoft.com...
>> >> > More stuff on tables... Will MS _ever_ get it right?
>> >> >
>> >> > I've got 2 tables with a blank line in between them. (They were
>> >> > created
>> >> > independly of each other, not by simply splitting one table into
>> >> > two.)
>> >> > Normally, if you remove the blank line between 2 tables the tables
>> >> > become
>> >> > 1
>> >> > automatically. However, sometimes (like this time) the tables stay
>> >> > as 2
>> >> > tables, even though there's nothing between them - not even a
>> >> > continuous
>> >> > section break. I really don't want to have to go through all the
>> >> > work
>> >> > of
>> >> > recreating a single table as the 2 tables are both quite complex -
>> >> > lots
>> >> > of
>> >> > varying column widths within groups of rows and styles and shading
>> >> > and
>> >> > borders, etc.
>> >> >
>> >> > Does anyone know of a way - either manually or through code - to
>> >> > force
>> >> > these
>> >> > two tables to concatenate?
>> >> >
>> >> > --
>> >> > Cheers!
>> >> > The Kiwi Koder
>> >> > (37 sleeps and counting...)
>> >>
>> >>
>> >>
>>
>>
>>

gordon(dot)bentleymix(at)gmail(dot)com>
Wed Dec 05 12:30:02 PST 2007

That's got it! Thanks, Doug. The hazards of working with someone else's
templates...
--
Cheers!
The Kiwi Koder


"Doug Robbins - Word MVP" wrote:

> The issue here was that one of the tables had the "Text wrapping" set to
> "Around" and for the other, it was set to "None".
>
> The setting must be the same to enable tables to be joined into one.
>
> --
> Hope this helps.
>
> Please reply to the newsgroup unless you wish to avail yourself of my
> services on a paid consulting basis.
>
> Doug Robbins - Word MVP
>
> "NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote in message
> news:364A6B0A-727F-41D6-BA21-E73803B74175@microsoft.com...
> > I'll send you a 'sanitised' version - just the segment of the doc that
> > contains the 'Troublesome Tables'. It's part of a much larger template,
> > but
> > I've confirmed that the problem still exists even when the tables in
> > question
> > are removed from their natural environment.
> > --
> > Cheers!
> > The Kiwi Koder
> >
> >
> > "Doug Robbins - Word MVP" wrote:
> >
> >> I'd be interested in seeing the document if you can share it.
> >>
> >> --
> >> Hope this helps.
> >>
> >> Please reply to the newsgroup unless you wish to avail yourself of my
> >> services on a paid consulting basis.
> >>
> >> Doug Robbins - Word MVP
> >>
> >> "NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote in
> >> message
> >> news:26330FE4-CF32-4520-A1D7-8368FB985609@microsoft.com...
> >> >A noble effort, Doug, but alas no joy. Now I have 3 separate tables: the
> >> > original 2 and a third with just a blank row in it below the second
> >> > one.
> >> > It's
> >> > not terribly important (yet) that it all be just one table, so I think
> >> > I'll
> >> > just leave it for now. If it becomes critical I guess I'll have to
> >> > rebuild
> >> > the table from scratch. :-(
> >> > --
> >> > Cheers!
> >> > The Kiwi Koder
> >> >
> >> >
> >> > "Doug Robbins - Word MVP" wrote:
> >> >
> >> >> Add a new row at the end of the first table, then select the second
> >> >> table
> >> >> and use Right Click Cut and then select the new row that you added to
> >> >> the
> >> >> first table and the Right Click and use Paste Rows. Then delete the
> >> >> empty
> >> >> row
> >> >>
> >> >> --
> >> >> Hope this helps.
> >> >>
> >> >> Please reply to the newsgroup unless you wish to avail yourself of my
> >> >> services on a paid consulting basis.
> >> >>
> >> >> Doug Robbins - Word MVP
> >> >>
> >> >> "NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote in
> >> >> message
> >> >> news:A5368E40-D7B9-4B74-A69D-D2866F8C8955@microsoft.com...
> >> >> > More stuff on tables... Will MS _ever_ get it right?
> >> >> >
> >> >> > I've got 2 tables with a blank line in between them. (They were
> >> >> > created
> >> >> > independly of each other, not by simply splitting one table into
> >> >> > two.)
> >> >> > Normally, if you remove the blank line between 2 tables the tables
> >> >> > become
> >> >> > 1
> >> >> > automatically. However, sometimes (like this time) the tables stay
> >> >> > as 2
> >> >> > tables, even though there's nothing between them - not even a
> >> >> > continuous
> >> >> > section break. I really don't want to have to go through all the
> >> >> > work
> >> >> > of
> >> >> > recreating a single table as the 2 tables are both quite complex -
> >> >> > lots
> >> >> > of
> >> >> > varying column widths within groups of rows and styles and shading
> >> >> > and
> >> >> > borders, etc.
> >> >> >
> >> >> > Does anyone know of a way - either manually or through code - to
> >> >> > force
> >> >> > these
> >> >> > two tables to concatenate?
> >> >> >
> >> >> > --
> >> >> > Cheers!
> >> >> > The Kiwi Koder
> >> >> > (37 sleeps and counting...)
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>

Julian
Thu Dec 06 08:09:13 PST 2007

Nice detective work Doug... any chance of a magnifying glass?

In particular - is there any (VBA) method for interating over an object's
properties without knowing what they are (but with some way to find out what
they are!) so that one could compare two objects (of the same class!) like
this to find such miscreants?

For i = 1 to objA.properties.count
If objA.properties(i) <> objB.properties(i) then
debug.print "Property " & objA.properties(i).name & " are
differerent" '... debug values etc.
Endif
Next

I can think of lots of uses for being to iterate over properties but have
never found a way to do it...

--
Julian I-Do-Stuff http:/berossus.blogspot.com - Stuff, Stuff and More Stuff

tooolnut
Thu May 15 05:06:02 PDT 2008

I'm having a similar problem joining tables that used to be one and the same
until I moved rows to rearrange them in the same table by selecting and
dragging. This was never a problem with Word 2003. The tables have the same
properties and yet they won't be joined no matter what I try, including your
suggestions here.

If there are slight differences in table properties which prevent them from
being joined, how does on copy and paste formatting only from one table to
another, without having to compare each property one at a time?

"Doug Robbins - Word MVP" wrote:

> The issue here was that one of the tables had the "Text wrapping" set to
> "Around" and for the other, it was set to "None".
>
> The setting must be the same to enable tables to be joined into one.
>
> --
> Hope this helps.
>
> Please reply to the newsgroup unless you wish to avail yourself of my
> services on a paid consulting basis.
>
> Doug Robbins - Word MVP
>
> "NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote in message
> news:364A6B0A-727F-41D6-BA21-E73803B74175@microsoft.com...
> > I'll send you a 'sanitised' version - just the segment of the doc that
> > contains the 'Troublesome Tables'. It's part of a much larger template,
> > but
> > I've confirmed that the problem still exists even when the tables in
> > question
> > are removed from their natural environment.
> > --
> > Cheers!
> > The Kiwi Koder
> >
> >
> > "Doug Robbins - Word MVP" wrote:
> >
> >> I'd be interested in seeing the document if you can share it.
> >>
> >> --
> >> Hope this helps.
> >>
> >> Please reply to the newsgroup unless you wish to avail yourself of my
> >> services on a paid consulting basis.
> >>
> >> Doug Robbins - Word MVP
> >>
> >> "NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote in
> >> message
> >> news:26330FE4-CF32-4520-A1D7-8368FB985609@microsoft.com...
> >> >A noble effort, Doug, but alas no joy. Now I have 3 separate tables: the
> >> > original 2 and a third with just a blank row in it below the second
> >> > one.
> >> > It's
> >> > not terribly important (yet) that it all be just one table, so I think
> >> > I'll
> >> > just leave it for now. If it becomes critical I guess I'll have to
> >> > rebuild
> >> > the table from scratch. :-(
> >> > --
> >> > Cheers!
> >> > The Kiwi Koder
> >> >
> >> >
> >> > "Doug Robbins - Word MVP" wrote:
> >> >
> >> >> Add a new row at the end of the first table, then select the second
> >> >> table
> >> >> and use Right Click Cut and then select the new row that you added to
> >> >> the
> >> >> first table and the Right Click and use Paste Rows. Then delete the
> >> >> empty
> >> >> row
> >> >>
> >> >> --
> >> >> Hope this helps.
> >> >>
> >> >> Please reply to the newsgroup unless you wish to avail yourself of my
> >> >> services on a paid consulting basis.
> >> >>
> >> >> Doug Robbins - Word MVP
> >> >>
> >> >> "NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote in
> >> >> message
> >> >> news:A5368E40-D7B9-4B74-A69D-D2866F8C8955@microsoft.com...
> >> >> > More stuff on tables... Will MS _ever_ get it right?
> >> >> >
> >> >> > I've got 2 tables with a blank line in between them. (They were
> >> >> > created
> >> >> > independly of each other, not by simply splitting one table into
> >> >> > two.)
> >> >> > Normally, if you remove the blank line between 2 tables the tables
> >> >> > become
> >> >> > 1
> >> >> > automatically. However, sometimes (like this time) the tables stay
> >> >> > as 2
> >> >> > tables, even though there's nothing between them - not even a
> >> >> > continuous
> >> >> > section break. I really don't want to have to go through all the
> >> >> > work
> >> >> > of
> >> >> > recreating a single table as the 2 tables are both quite complex -
> >> >> > lots
> >> >> > of
> >> >> > varying column widths within groups of rows and styles and shading
> >> >> > and
> >> >> > borders, etc.
> >> >> >
> >> >> > Does anyone know of a way - either manually or through code - to
> >> >> > force
> >> >> > these
> >> >> > two tables to concatenate?
> >> >> >
> >> >> > --
> >> >> > Cheers!
> >> >> > The Kiwi Koder
> >> >> > (37 sleeps and counting...)
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>

Stefan
Thu May 15 05:40:43 PDT 2008

What goes wrong? If both tables have "Text wrapping" set to "None" it should
be a straightforward task to delete the paragraph mark(s) between tables to
merge them. To see what you are doing, you may want to display nonprinting
marks (Ctrl+Shift+8 toggles their display).

Note that if you are saying that column widths do not match, you can fix
that by holding the Alt key while dragging the border (or gridline, if no
borders are displayed) in place.

--
Stefan Blom
Microsoft Word MVP


"tooolnut" wrote in message
news:06A5D935-A331-4520-8C9A-A03A8D0C0F4F@microsoft.com...
> I'm having a similar problem joining tables that used to be one and the
> same
> until I moved rows to rearrange them in the same table by selecting and
> dragging. This was never a problem with Word 2003. The tables have the
> same
> properties and yet they won't be joined no matter what I try, including
> your
> suggestions here.
>
> If there are slight differences in table properties which prevent them
> from
> being joined, how does on copy and paste formatting only from one table to
> another, without having to compare each property one at a time?
>
> "Doug Robbins - Word MVP" wrote:
>
>> The issue here was that one of the tables had the "Text wrapping" set to
>> "Around" and for the other, it was set to "None".
>>
>> The setting must be the same to enable tables to be joined into one.
>>
>> --
>> Hope this helps.
>>
>> Please reply to the newsgroup unless you wish to avail yourself of my
>> services on a paid consulting basis.
>>
>> Doug Robbins - Word MVP
>>
>> "NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote in
>> message
>> news:364A6B0A-727F-41D6-BA21-E73803B74175@microsoft.com...
>> > I'll send you a 'sanitised' version - just the segment of the doc that
>> > contains the 'Troublesome Tables'. It's part of a much larger template,
>> > but
>> > I've confirmed that the problem still exists even when the tables in
>> > question
>> > are removed from their natural environment.
>> > --
>> > Cheers!
>> > The Kiwi Koder
>> >
>> >
>> > "Doug Robbins - Word MVP" wrote:
>> >
>> >> I'd be interested in seeing the document if you can share it.
>> >>
>> >> --
>> >> Hope this helps.
>> >>
>> >> Please reply to the newsgroup unless you wish to avail yourself of my
>> >> services on a paid consulting basis.
>> >>
>> >> Doug Robbins - Word MVP
>> >>
>> >> "NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote in
>> >> message
>> >> news:26330FE4-CF32-4520-A1D7-8368FB985609@microsoft.com...
>> >> >A noble effort, Doug, but alas no joy. Now I have 3 separate tables:
>> >> >the
>> >> > original 2 and a third with just a blank row in it below the second
>> >> > one.
>> >> > It's
>> >> > not terribly important (yet) that it all be just one table, so I
>> >> > think
>> >> > I'll
>> >> > just leave it for now. If it becomes critical I guess I'll have to
>> >> > rebuild
>> >> > the table from scratch. :-(
>> >> > --
>> >> > Cheers!
>> >> > The Kiwi Koder
>> >> >
>> >> >
>> >> > "Doug Robbins - Word MVP" wrote:
>> >> >
>> >> >> Add a new row at the end of the first table, then select the second
>> >> >> table
>> >> >> and use Right Click Cut and then select the new row that you added
>> >> >> to
>> >> >> the
>> >> >> first table and the Right Click and use Paste Rows. Then delete
>> >> >> the
>> >> >> empty
>> >> >> row
>> >> >>
>> >> >> --
>> >> >> Hope this helps.
>> >> >>
>> >> >> Please reply to the newsgroup unless you wish to avail yourself of
>> >> >> my
>> >> >> services on a paid consulting basis.
>> >> >>
>> >> >> Doug Robbins - Word MVP
>> >> >>
>> >> >> "NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote
>> >> >> in
>> >> >> message
>> >> >> news:A5368E40-D7B9-4B74-A69D-D2866F8C8955@microsoft.com...
>> >> >> > More stuff on tables... Will MS _ever_ get it right?
>> >> >> >
>> >> >> > I've got 2 tables with a blank line in between them. (They were
>> >> >> > created
>> >> >> > independly of each other, not by simply splitting one table into
>> >> >> > two.)
>> >> >> > Normally, if you remove the blank line between 2 tables the
>> >> >> > tables
>> >> >> > become
>> >> >> > 1
>> >> >> > automatically. However, sometimes (like this time) the tables
>> >> >> > stay
>> >> >> > as 2
>> >> >> > tables, even though there's nothing between them - not even a
>> >> >> > continuous
>> >> >> > section break. I really don't want to have to go through all the
>> >> >> > work
>> >> >> > of
>> >> >> > recreating a single table as the 2 tables are both quite
>> >> >> > complex -
>> >> >> > lots
>> >> >> > of
>> >> >> > varying column widths within groups of rows and styles and
>> >> >> > shading
>> >> >> > and
>> >> >> > borders, etc.
>> >> >> >
>> >> >> > Does anyone know of a way - either manually or through code - to
>> >> >> > force
>> >> >> > these
>> >> >> > two tables to concatenate?
>> >> >> >
>> >> >> > --
>> >> >> > Cheers!
>> >> >> > The Kiwi Koder
>> >> >> > (37 sleeps and counting...)
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>

tooolnut
Thu May 15 06:00:01 PDT 2008

Thanks for your prompt assistance, Stefan.

There is no paragraph mark: the tables appear to be welded together, except
that the horizontal gridline separating them is heavier. The column widths
are identical, as far as I can tell, but this shouldn't be the reason they
cannot be joined, as it should be possible to have cells and columns of
differing sizes in the same table; at least that's how it's always been
before WORD 2007.

"Stefan Blom" wrote:

> What goes wrong? If both tables have "Text wrapping" set to "None" it should
> be a straightforward task to delete the paragraph mark(s) between tables to
> merge them. To see what you are doing, you may want to display nonprinting
> marks (Ctrl+Shift+8 toggles their display).
>
> Note that if you are saying that column widths do not match, you can fix
> that by holding the Alt key while dragging the border (or gridline, if no
> borders are displayed) in place.
>
> --
> Stefan Blom
> Microsoft Word MVP
>
>
> "tooolnut" wrote in message
> news:06A5D935-A331-4520-8C9A-A03A8D0C0F4F@microsoft.com...
> > I'm having a similar problem joining tables that used to be one and the
> > same
> > until I moved rows to rearrange them in the same table by selecting and
> > dragging. This was never a problem with Word 2003. The tables have the
> > same
> > properties and yet they won't be joined no matter what I try, including
> > your
> > suggestions here.
> >
> > If there are slight differences in table properties which prevent them
> > from
> > being joined, how does on copy and paste formatting only from one table to
> > another, without having to compare each property one at a time?
> >
> > "Doug Robbins - Word MVP" wrote:
> >
> >> The issue here was that one of the tables had the "Text wrapping" set to
> >> "Around" and for the other, it was set to "None".
> >>
> >> The setting must be the same to enable tables to be joined into one.
> >>
> >> --
> >> Hope this helps.
> >>
> >> Please reply to the newsgroup unless you wish to avail yourself of my
> >> services on a paid consulting basis.
> >>
> >> Doug Robbins - Word MVP
> >>
> >> "NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote in
> >> message
> >> news:364A6B0A-727F-41D6-BA21-E73803B74175@microsoft.com...
> >> > I'll send you a 'sanitised' version - just the segment of the doc that
> >> > contains the 'Troublesome Tables'. It's part of a much larger template,
> >> > but
> >> > I've confirmed that the problem still exists even when the tables in
> >> > question
> >> > are removed from their natural environment.
> >> > --
> >> > Cheers!
> >> > The Kiwi Koder
> >> >
> >> >
> >> > "Doug Robbins - Word MVP" wrote:
> >> >
> >> >> I'd be interested in seeing the document if you can share it.
> >> >>
> >> >> --
> >> >> Hope this helps.
> >> >>
> >> >> Please reply to the newsgroup unless you wish to avail yourself of my
> >> >> services on a paid consulting basis.
> >> >>
> >> >> Doug Robbins - Word MVP
> >> >>
> >> >> "NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote in
> >> >> message
> >> >> news:26330FE4-CF32-4520-A1D7-8368FB985609@microsoft.com...
> >> >> >A noble effort, Doug, but alas no joy. Now I have 3 separate tables:
> >> >> >the
> >> >> > original 2 and a third with just a blank row in it below the second
> >> >> > one.
> >> >> > It's
> >> >> > not terribly important (yet) that it all be just one table, so I
> >> >> > think
> >> >> > I'll
> >> >> > just leave it for now. If it becomes critical I guess I'll have to
> >> >> > rebuild
> >> >> > the table from scratch. :-(
> >> >> > --
> >> >> > Cheers!
> >> >> > The Kiwi Koder
> >> >> >
> >> >> >
> >> >> > "Doug Robbins - Word MVP" wrote:
> >> >> >
> >> >> >> Add a new row at the end of the first table, then select the second
> >> >> >> table
> >> >> >> and use Right Click Cut and then select the new row that you added
> >> >> >> to
> >> >> >> the
> >> >> >> first table and the Right Click and use Paste Rows. Then delete
> >> >> >> the
> >> >> >> empty
> >> >> >> row
> >> >> >>
> >> >> >> --
> >> >> >> Hope this helps.
> >> >> >>
> >> >> >> Please reply to the newsgroup unless you wish to avail yourself of
> >> >> >> my
> >> >> >> services on a paid consulting basis.
> >> >> >>
> >> >> >> Doug Robbins - Word MVP
> >> >> >>
> >> >> >> "NZ VBA Developer" <gordon(dot)bentleymix(at)gmail(dot)com> wrote
> >> >> >> in
> >> >> >> message
> >> >> >> news:A5368E40-D7B9-4B74-A69D-D2866F8C8955@microsoft.com...
> >> >> >> > More stuff on tables... Will MS _ever_ get it right?
> >> >> >> >
> >> >> >> > I've got 2 tables with a blank line in between them. (They were
> >> >> >> > created
> >> >> >> > independly of each other, not by simply splitting one table into
> >> >> >> > two.)
> >> >> >> > Normally, if you remove the blank line between 2 tables the
> >> >> >> > tables
> >> >> >> > become
> >> >> >> > 1
> >> >> >> > automatically. However, sometimes (like this time) the tables
> >> >> >> > stay
> >> >> >> > as 2
> >> >> >> > tables, even though there's nothing between them - not even a
> >> >> >> > continuous
> >> >> >> > section break. I really don't want to have to go through all the
> >> >> >> > work
> >> >> >> > of
> >> >> >> > recreating a single table as the 2 tables are both quite
> >> >> >> > complex -
> >> >> >> > lots
> >> >> >> > of
> >> >> >> > varying column widths within groups of rows and styles and
> >> >> >> > shading
> >> >> >> > and
> >> >> >> > borders, etc.
> >> >> >> >
> >> >> >> > Does anyone know of a way - either manually or through code - to
> >> >> >> > force
> >> >> >> > these
> >> >> >> > two tables to concatenate?
> >> >> >> >
> >> >> >> > --
> >> >> >> > Cheers!
> >> >> >> > The Kiwi Koder
> >> >> >> > (37 sleeps and counting...)
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>
>
>

Stefan
Thu May 15 06:10:34 PDT 2008

Switch to Draft view. Is there a continuous section break between the
tables? If so, delete it.

--
Stefan Blom
Microsoft Word MVP


"tooolnut" wrote in message
news:4DF8769D-513A-4C1E-B5AA-FCCB7A7D9C9B@microsoft.com...
> Thanks for your prompt assistance, Stefan.
>
> There is no paragraph mark: the tables appear to be welded together,
> except
> that the horizontal gridline separating them is heavier. The column widths
> are identical, as far as I can tell, but this shouldn't be the reason they
> cannot be joined, as it should be possible to have cells and columns of
> differing sizes in the same table; at least that's how it's always been
> before WORD 2007.
>
> "Stefan Blom" wrote:
>
>> What goes wrong? If both tables have "Text wrapping" set to "None" it
>> should
>> be a straightforward task to delete the paragraph mark(s) between tables
>> to
>> merge them. To see what you are doing, you may want to display
>> nonprinting
>> marks (Ctrl+Shift+8 toggles their display).
>>
>> Note that if you are saying that column widths do not match, you can fix
>> that by holding the Alt key while dragging the border (or gridline, if no
>> borders are displayed) in place.
>>
>> --
>> Stefan Blom
>> Microsoft Word MVP
>>
>>
>> "tooolnut" wrote in message
>> news:06A5D935-A331-4520-8C9A-A03A8D0C0F4F@microsoft.com...
>> > I'm having a similar problem joining tables that used to be one and the
>> > same
>> > until I moved rows to rearrange them in the same table by selecting and
>> > dragging. This was never a problem with Word 2003. The tables have the
>> > same
>> > properties and yet they won't be joined no matter what I try, including
>> > your
>> > suggestions here.
>> >
>> > If there are slight differences in table properties which prevent them
>> > from
>> > being joined, how does on copy and paste formatting only from one table
>> > to
>> > another, without having to compare each property one at a time?
>> >
>> > "Doug Robbins - Word MVP" wrote:
>> >
>> >> The issue here was that one of the tables had the "Text wrapping" set
>> >> to
>> >> "Around" and for the other, it was set to "None".
>> >>
>> >> The setting must be the same to enable tables to be joined into one.
>> >>
>> >> --
>> >> Hope this helps.
>> >>
>> >> Please reply to the newsgroup unless you wish to avail yourself of my
>> >> service