DXL - Table row limit help!

HCL Domino Domino Forum
1

Hi

I’m creating a table using a script and DXL.

I get the following error when I try to create one particular table with a lot of rows using

Set dmp = session.CreateDXLIMporter(stream, db)Call dmp.Process.

“Count plus existing rows exceeds max rows of 255.”

I’m assuming this means that you can only have 255 rows for a table but is there a way to somehow bypass this and create as many rows as you would like?

Hope someone can give me an answer

Thanks :slight_smile:

2

Subject: DXL - Table row limit help!

This is a hard and fast limit on tables in Notes/Domino (see Domino Limits). You will have to create multiple tables, and I would recommend that each be about 100 rows, just because really large tables render very slowly.

3

Subject: RE: DXL - Table row limit help!

Hi Ben

Thanks for that - I was just wondering if there was a way around it. I just had to close the table and then create a new one underneath for every 250 rows. I will probably change it to 100 just to see the difference in performance - if any.

Thanks again!

4

Subject: RE: DXL - Table row limit help!

Make sure that between the tables in DXL you have at least a paragraph element, otherwise you may end up crashing Notes when a specific paragraph grows bigger than 64KB. (been there, done that).

cheers,

Bram

5

Subject: DXL - Table row - Maximum Number of Memory segments exceeded

Hi again

I’m getting the error message “maxium number of memory segments that notes can support has been exceeded” when I try to script out a table with 1000 rows (I’m breaing up the tables into 100s) Does anyone know what this message means? Bram has mentioned that I should have at least a paragraph element between tables but does this mean

or

I think my notesstream is over 64kb when I call the dmp.process - would this be the problem? What should I do to avoid this?

By the way thanks Stan for the input - the other problem had to do with using

}& variable & {

where the variable contained a “&” - this would cause a “Expected entity name for reference” problem - I assume that the dmp.process method thinks that I didnt close the variable off correctly?

hope someone can give me some advice on the “maxium number of memory segments that notes can support has been exceeded” error

Thanks

6

Subject: RE: DXL - Table row - Maximum Number of Memory segments exceeded

The tag for a new paragraph is

– not

7

Subject: *Good point.

8

Subject: RE: DXL - Table row limit help!

On the subject of rich text, you can pretty much rely on it that Ben knows what he’s talking about

9

Subject: *Thanks

10

Subject: A bit more information on performance

I was doing a bit of testing, and it appears that in ND6, most of the performance advantage of smaller tables has been eliminated. It is still a bit faster with smaller tables, especially if they have anything “fancy” such as merged cells, but not enough to worry about. Any cell merging and I would definitely stick to smaller tables, as there tends to be a performance hit there in any case.

11

Subject: RE: A bit more information on performance

Hi Ben and everyone else

Thanks for all the info - its good to get all this insight.

I have another question but I’ve posted it as another topic although it has to do with DXL and tables.

Its to do with having an ampersand in a piece of text and passing it to a sub which creates a row. Anyway if you see it in the forum I would really like to hear your advice.

Thanks again.

12

Subject: RE: A bit more information on performance

A literal ampersand in DXL needs to be an “entity” – &.

13

Subject: *I answered above, and I think Stan just answered as well.