Table is malformed

HCL Domino Domino Forum
1

Hi:

I can’t open a document and get error ‘Table is malformed’

Server & Client 6.0.1CF1

DB ODS 43

Database is about 800MB

It only happends with this document, any idea of how to solve this problem?

Tried:

load fixup -F -J

load updall -R -C

load compact -c -L -i

with no luck,

J R

2

Subject: Table is malformed

HI, I have seen a couple posts on this… but no solution. I have just run across the same thing. I do have several embedded views… could this be related? Any other ideas?

THANKS!

3

Subject: Table is malformed

Hi - I have just run into the same issue. Were you able to resolve your problem. My form does have embedded views… and a table with tabs on the side… but other docs in the database open without a problem. Any ideas?

THANKS!

4

Subject: RE: Table is malformed

Hi Mimi:

It is still happening here with server & client 6.0.2CF2.

I don’t think it has relation with embedded view since our database doesn’t have any one.

See you,

J R

5

Subject: Table is malformed

Hello

I received the very same error on opening an email with my R6 client. My customer who used an R5 client received a red box and then notes crashed. I found out that this was due to the fact that the email was sent back and forth and the last person who sent the email to my customer used the Outlook Editor. In this way the tracking script became corrupt and therefore notes was no more able to read the email.

You can see that in the document properties in the entry $mailer: the corrupt email contained IBM Lotus Notes Access for MS Outlook (XP) Build.

When the sender sent the very same mail via his notes, there was no problem, when he sent the very same mail and removed the graphic from the tracking (an envelope with a flame) which was attached instead of incorporated in the mail he could send the message via Outlook and the receiver could open the email without problems.

Hope this helps

chatake

6

Subject: Table is malformed

I had twice a similar problem with tables in sections contained in a rich text field. In both cases there were many attachments in these tables. In both cases the total size of the summary fields was higher than for the other documents in the db. (I don’t know whether this is relevant, but it’s a fact.)I somehow salvaged my documents by creating (via LotusScript) a new document in which I copied all fields but the rich text field containing the tables within sections and the attachements. I detached the attachments and reattached them using LotusScript, and I turned the summary property of most fields to False. The owners of the documents could then recreate the tables, and the new documents were ok. I’d be glad to have a better solution to the problem.