Results 1 to 6 of 6
  1. #1
    jeffz
    Guest

    Vertically Merged Cells Dangerous in W2K?

    At my workplace, a Presentation Center for an Investment Bank, we have to follow strict formatting rules because many people work on documents at various stages of their production.

    One rule is NEVER to use Vertically Merged cells in a table, because "it can cause corruption of the document."

    Sometimes, the easiest way to insert a PPT graphic next to several rows in the table would be to use vertically merged cells. Instead, we are supposed to jump through several hoops by creating snaking columns with two tables, then playing around to make the tables line up properly. A real PITA! [img]/w3timages/icons/sad.gif[/img]

    Can anyone point me to evidence that this feature can REALLY cause doc corruption?

    Thanks

  2. #2
    Super Moderator
    Join Date
    Dec 2000
    Location
    New York, NY
    Posts
    2,970
    Thanks
    3
    Thanked 29 Times in 27 Posts

    Re: Vertically Merged Cells Dangerous in W2K?

    Jeff,

    That workaround does sound like a pain.
    I've never seen vertically merged cells cause a document to corrupt, but I have seen them cause two classes of problems:

    If you run a macro that loops through all the cells, rows or columns in a table, on a table that contains vertically merged cells, the macro will often give bad results or bomb.

    Running a CompareRite on a document that contains vertically merged table cells, can cause bad results (I think DeltaView does handle these though).

    Maybe one of the above reasons, or a similar one, was the original cause for this edict.

  3. #3
    Platinum Lounger
    Join Date
    Dec 2000
    Location
    Queanbeyan, New South Wales, Australia
    Posts
    3,730
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Vertically Merged Cells Dangerous in W2K?

    Gidday,

    I've seen problems in Excel with merged cells- but if you know there's a possibility there, you can check if a cell is merged.

    There's a possible problem in Word if yo gou through rows in Column 1, but you miss on cells in column 2.
    Subway Belconnen- home of the Signboard to make you smile. Get (almost) daily updates- follow SubwayBelconnen on Twitter.

  4. #4
    5 Star Lounger
    Join Date
    Dec 2000
    Location
    Tallahassee, Florida, USA
    Posts
    901
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Vertically Merged Cells Dangerous in W2K?

    Another possible reason for the edict: Not everyone who works on the document has Word 2K... but the work-around would cause as many problems with round-tripping as the merged verticals (if not more). I've been working with both DeltaView (2.5.175) and Word 2K(SR1(a)), and never seen problems with vertically merged cells.

    One feature we don't use, which may be driving your management's policy... Word's versioning and track/changes feature (We use a document management system). If so, that may open a whole new can of worms, and someone should probably tell "them" [img]/w3timages/icons/alien.gif[/img] about metadata.
    Karen

  5. #5
    jeffz
    Guest

    Re: Vertically Merged Cells Dangerous in W2K?

    I think you hit the proverbial nail on the head. We DO use a lot of macros that loop through tables for various reasons and I imagine that this is the reason for the edict.

    If I were King of the Forest, I would change the rule to: "Don't use our table macros on tables with vertically merged cells, OR ELSE you will run into problems."

    Thanks for your help.

  6. #6
    jeffz
    Guest

    Re: Vertically Merged Cells Dangerous in W2K?

    Thanks for the response.

    But to clarify, this is a Presentation Center, meaning that we're sort of a high-powered "document factory" serving other departments. All operators have exactly the same setup, W2K, and our "clients" do not have edit privileges on the finished docs.

    Also, we use document management software, PCDocs, and we don't use the versioning features in W2K because they cause documents to BLOAT [img]/w3timages/icons/tonguea.gif[/img] horribly and can lead to enormous files that take forever to save or can really get corrupt.

    I think the macro aspect explains our "rule."

    --
    Jeff

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •