Removing table autoformatting

[Alex]

Hello,

Assume there is a table in a document with AutoFormat properties applied.

Can I remove the AutoFormat properties without changing the table's current appearance (basically "freezing" the table's current format)?

Thanks.


Best wishes,
Alex.

 

[Alex]

Hello,

Assume there is a table in a document with AutoFormat properties applied.

Can I remove the AutoFormat properties without changing the table's current appearance
(basically "freezing" the table's current format)?

Thanks.

Anyone?

 

[Alex]

I was under the impression that paid MS employees monitor these groups and help MSDN subscribers who post here.
Was I mistaken?

Hello,

Assume there is a table in a document with AutoFormat properties applied.

Can I remove the AutoFormat properties without changing the table's current appearance
(basically "freezing" the table's current format)?

Thanks.

Best regards,
Alex.

 

[Chip Pearson]

You are under the wrong impression. These newsgroups are
peer-to-peer, user-to-user forums.


--
Cordially,
Chip Pearson
Microsoft MVP - Excel
Pearson Software Consulting, LLC
www.cpearson.com


I was under the impression that paid MS employees monitor these
groups and help MSDN subscribers who post here.
Was I mistaken?

Hello,

Assume there is a table in a document with AutoFormat
properties applied.

Can I remove the AutoFormat properties without changing the
table's current appearance
(basically "freezing" the table's current format)?

Thanks.

Best regards,
Alex.

 

[Klaus Linke]

Hi Alex,

You probably got no reply because nobody understood your question... I
didn't.

The properties *are* the appearance, so you can not "remove" them.

If you mean: Can I freeze the current layout so that nobody can change it
any more (= can only edit the text), then maybe protected forms are your
ticket. Or the protection mechanisms in Word2003, if you use that.

If you describe what you want to achieve, maybe you'll get more detailed
tipps.

Regards,
Klaus




I was under the impression that paid MS employees monitor these groups and
help MSDN subscribers who post here.
Was I mistaken?

Hello,

Assume there is a table in a document with AutoFormat properties applied.

Can I remove the AutoFormat properties without changing the table's
current appearance
(basically "freezing" the table's current format)?

Thanks.

Best regards,
Alex.

 

[Alex]

Hello Klaus, thanks for your reply.

You probably got no reply because nobody understood your question... I
didn't.

Fair enough, I'll try to be more precise.

The properties *are* the appearance, so you can not "remove" them.

If you mean: Can I freeze the current layout so that nobody can change it
any more (= can only edit the text)

Not exactly.

Let's say I create a 10x10 table.

Then I apply the wdTableFormatProfessional (for example) auto-format to it.
Now I have a nicely formatted table, whose 1st row is white on black bold and the rest are black on white.

I would like those formatting properties to stay that way unless the user manually changes them

However, there is a problem:

If I split the table along, say, row #5 - I will get two tables, but this row (which was row #5 in the original table but is now row #1 in the second table) will change its format according to the auto-format that was applied originally.

This is exactly what I am trying to avoid.
My process needs to split the table but without auto-format kicking in and reformatting it.

So, is there a way to apply the auto-formatting normally but before splitting the table marking it as not auto-formatted (but without resetting the current format)?


Thanks,
Alex.

 

[Klaus Linke]

Hi Alex,

Thank you for the explanation!

Sorry, but there isn't a way to freeze the formatting in this way. You might
be able to write a macro, but it probably would have to remember hundreds or
thousands of properties (borders, shading, textures, colors, padding... of
each cell), and would be slow. Such a solution would also be difficult to
maintain (because a later modification of the table style would no longer
affect the table, and if you'd apply a different table style later, the
problem would reappear).

If it's just the heading row that makes a difference, then maybe just
turning off heading rows in the lower part of the table might do the trick?

Selection.Tables(1).ApplyStyleHeadingRows = False

If the scenario is more complex (banded rows ...), you might create a
special table style for the second part of the table, with the proper
formatting.

Regards,
Klaus



Hello Klaus, thanks for your reply.

You probably got no reply because nobody understood your question... I
didn't.

Fair enough, I'll try to be more precise.

The properties *are* the appearance, so you can not "remove" them.

If you mean: Can I freeze the current layout so that nobody can change it
any more (= can only edit the text)

Not exactly.

Let's say I create a 10x10 table.

Then I apply the wdTableFormatProfessional (for example) auto-format to it.
Now I have a nicely formatted table, whose 1st row is white on black bold
and the rest are black on white.

I would like those formatting properties to stay that way unless the user
manually changes them

However, there is a problem:

If I split the table along, say, row #5 - I will get two tables, but this
row (which was row #5 in the original table but is now row #1 in the second
table) will change its format according to the auto-format that was applied
originally.

This is exactly what I am trying to avoid.
My process needs to split the table but without auto-format kicking in and
reformatting it.

So, is there a way to apply the auto-formatting normally but before
splitting the table marking it as not auto-formatted (but without resetting
the current format)?


Thanks,
Alex.

 

[Klaus Linke]

I just tried with the "Table Professional" style: If your process formats
the paragraph mark between the tables as "hidden", you might also want to
remove the top border from the lower table's first row.

With Selection.Tables(1).Rows(1).Cells
.Borders(wdBorderTop).LineStyle = wdLineStyleNone
End With


Maybe if you explain why your process needs to split the table in the first
place, someone might be able to suggest a way to achieve that without
splitting the table.
I do split tables frequently because Word docs with large tables become
sluggish to edit ... unfortunately, there isn't much else you can do to
avoid that. One thing that helps a bit is to set the table width (AutoFit)
to "fixed".

Greetings,
Klaus

 

[Alex]

Maybe if you explain why your process needs to split the table in the first
place, someone might be able to suggest a way to achieve that without
splitting the table.

The add-in converts the document contents into a format that is used as input to another application.
It expects a split table so we have to provide it one.

I do split tables frequently because Word docs with large tables become
sluggish to edit ... unfortunately, there isn't much else you can do to
avoid that. One thing that helps a bit is to set the table width (AutoFit)
to "fixed".

Best wishes,
Alex.