Is there any way i can set a property in an edit table so that when the form opens in runtime the edittable already has the specified number of blank lines inserted in it. Say 10000.

Thanks

set_property(@Window:".mybloodybigeditable","LIST",str(@fm,10000))

I would also suggest you have set to -1

Thanks for your inputs but the whole idea of this question was to do it without using Set_property or Send _message as it takes a lot of processing time in setting the property of the edittable. I need something that is quick.

Thanks.

Your original request was somewhat confusing as you requested the ability to "set a property in an edit table". I guess what was more important to you was that "the edittable already has the specified number of blank lines inserted in it".

In that regard, there is nothing available to do that. However…if you are open to using OLE and waiting a little while you can employ an ActiveX edittable control. OI 7.1 will allow you to specify property values at design-time (very cool). If the edittable controls permits some kind of initial row count then this might give you what you want.

BTW, even if you could indicate the preset number of rows for the OI edittable, it would seem to me that OI would ultimately use the same commands you would in Basic+ to structure the control. Therefore I'm not sure you would see any speed benefits. Perhaps there are better (i.e. more low-level) ways of getting this many rows in the edittable.

dbakke@srpcs.com

SRP Computer Solutions, Inc.

Why do you need the edittable preset to 10,000 lines?

Maybe if we know the problem, there could be another 'solution'

Actually we have 2 Openinsight tables linked together with a relational index just like a Master-Detail relationship. So for each record in the master table we can have multiple records in the detail table.

In our application for each master record there can be as many as 5000-10000 detail records. In our entry form when the user retrieves the master record we populate an edittable with all the corresponding detail records using a procedure. It works alright for jobs with 1500-2000 records but when detail records are more than that the system becomes slower and slower.

We have tried all sorts of things and came to a conclusion that OI retrieves data pretty quickly but it it slower in populating that data using 'INSERT' in the edittable as it has to create new lines in it but if we have an edittable with blank lines already in it then OI populates data pretty quickly using TEXT_BY_POS as it need not create new lines in the edittable.

Thanks again

Have you tried building your "Table" with the data in memory and then setting the LIST property with this value

set_property(@Window:".mybloodybigeditable","LIST",My10000RowDataTable))

Prashant,

Could't you use a combination of both? Say insert 1000 lines, populate them, insert the next thousand etc…

I've timed these cases to add 10000 rows:

1) Raw API SendMessage calls to insert the blank rows

2) Send_Message INSERT calls one at a time

3) Send_Message INSERT calls in blocks of 1000

4) Setting the LIST property

The results were:

(4) fastest

(1)

(3)

(2) slowest

And there generally wasn't too much difference between the top three.

The Sprezzatura Group

World leaders in all things RevSoft

Tried that already didn't make much of a difference

Thanks

We have aleready tried all these things and came to a conclusion that OI takes time in creating the blank lines or inserting lines in the edittable. So If we can get an edittable with specified no of blank lines on it than we can populate the data pretty quickly.

Thanks

There is a significant difference in the timings for the creation of a 10,000 line table in my tests depending on the following variables:

No of columns

The value of Width for each column must be the minium possible

The value of Data Length must be the minimum possible.

if 80/80 and 5 columns I get 13 secs. If 1/1 and 1 column I get 0 secs.

Barry

PS:

It is the Data Length that is the most significant factor.

Thanks for your inputs

We have an edit table with 27 columns and most of the Data Lengths

are 80 except 2 columns with 400(Item descriptions). But later on in some of our screens we may have an edit table with 200 columns or more. What will happen there then? I am getting a bit worried thinking about all this now

View this thread on the forum...