LiveCode Forums.

I am trying to create a datagrid that has 1179 columns (with my current set of data) with labels that come in at 26,431 chars, including the returns for the seperators in the list I am using to set the property.

The datagrid itself (the non-heading part) has 25,757 rows, with 3,929,615 chars, most of which are the returns & tabs needed to seperate the items into columns and rows (this is a table showing maingram dataset access - datasets across the top, users and groups down the side, where they intersect and access specifically granted to the dataset - so there are a LOT of empty cells).

Anyway, I can buiold are the datastructures I need in variables, but attmepting to pop eventhing into an existing datagrid causes a complete lockup and eventual force quit.

Any ideas? Am I breaking rules by having so many columns? Do I run into the long single line rules becasue of the way that the datagrid control handles things internally? Am I doomed to wander this howling, ghost haunted wasteland forever?

I suppose if I had to I could paginate everything to a max number of columns, but it's a huge hassle in a already complex program...

Thanks for any assitance or shed light.

Hi Ed,

please load the DataGrid docs as PDF here:
http://lessons.runrev.com/m/datagrid
and read the section: Advanced Options, chapter: Displaying Large Amounts of Data!

I did not work with this yet, but sounds as if this is what you need to do before your machine explodes!


Best

Klaus

Thanks Klaus. I had looked at this and while it makes handling the number of rows potentially easier, it doesn't seem to address the length of the headers and the length of the rows. Right now just setting the header to such a large number of columns makes it blow up, as does trying to trying to set even a single row to the data that I want (which would still auto create 1179 columns).

I think I am going to have to do some behind the scenes manipulation - have the full data in a global variable as an array or something, then create a, say, 200 (to be safe) item "window" on that that the user can scroll through. It's annoying, but it should work. I will probably be back here as I try to figure that out...

Hi Ed,

ah, sorry I overlooked 1179 ROWS!
Not showing all rows on the screen is surely the way to go and to avoid this GUI nightmare

Anyway, maybe you should ask RunRev (support@runrev.com) what the limits of a datagrids may be.


Best

Klaus

It may be that the cell group containing the 1179 columns exceeds the limits of the size of groups (32,767 px).

Since that many columns is likely overwhelming to the user anyway, I'd second Klaus' suggestion of coming up with a subset of those the user can do meaningful work with.

Ah - that's probably what it is - I hadn't realized there was a 32K px width limit on groups as well.

I think I have something that works for creating a 200 column window that I can use the page left and right through the columns of data. Luckily the full set of columns is something that very few people ever need to deal with - normal users with see a set taht just includes the columns that have access they actually need to review. Pretty much the audience for the full data is just me and the person that has to review the computer operations groups access (they have a lot of access...). I've experimented with a lot of presentation options over the last few years and this method - datasets across the top, users/groups/members on the left and access at the intersection seems to be the most understandable for people and the one that makes them the most likely to actually perform the review as opposed to just rubber stamp, so I think I am stuck with occaionally having a lot of columns.

This is all coming up now becasue after 5 years we have switched from reviewing a subset of "sensitive" datasets to reviewing *everything*, so it's sort of like having to do a review of every folder on your hard disk. So, all the stuff that I wrote ages ago that worked fine is blowing up under the increased load...