Hi All

In my epic build of a workaround for problems associated with very large records, I was working around some of the problems associated with the size limit of an edit table (edittable) by building a paging system.

Unfortunately (?) I stored the unformatted data for the table in an editbox.

ie

void=SET_PROPERTY(@window : ".MY_TEXT", "TEXT", unfmt_extract)

what I found was when unfmt_extract got close to 64KB (65536 bytes)

ie 64510 bytes or even 63800 bytes that the Text property of my edit box was being cleared instead of holding my data. From debug, unfmt_extract had data but when I retrieved from MY_TEXT, there was no data. I had no problems with smaller records ie around 30000 bytes.

This doesn't happen if I use

void=SET_PROPERTY(@window, "@MY_DATA", unfmt_extract)

Ie this @Var will hold more data than the text box.

I assume all bets are off when I do get close to 65536 because the variable unfmt_extract will die.

And I was boundary testing. I hope my client never gets to this limit, unless they are prepared to fund a data restructure.

Why does the edit box hold less data than the @Var? What is the edit box limit?

Scott

Scott,

Edit controls (both single (EDITLINE) and multi-line (EDITBOX) ) are basically limited in Win16 to a 32KB data size.

With some extra programming ('but you'll have to do this it in C') you can push a multiline Edit control to somewhere near 64KB, but don't bet on this.

There used to be a great article on this on the MSDN web-site but then M$ forgot that they did 16-bit stuff and removed it. If you have an MSDN subscription with the CD's then you'll probably find it in the Archive CD Set.

The Sprezzatura Group

World leaders in all things RevSoft

Hi Sprezz

What keywords would you look for in that archive? I'm not much into C programming, it always seemed like a good thing to know about but I never quite got round-tuit. I do have access to MSDN stuff.

With what workaround I do have, even though the original setup involved editlines or editboxes to hold the unformatted data and edit tables to hold the pages I managed to make the system go from a limit 10 000 bytes and about 50 lines to work with around 25000 bytes and 200 lines. When I changed to the @Var it now works reasonably politely with 63000 bytes and 750 lines of stuff.

Probably what I need is the edittable page loading system combined with a data restructure so each "line" is its own record in another table. Then I could have as many lines as I (or my clients) like. The system would get very slow though as each line has to be validated against every other line to prevent "overlaps". Takes a good ten minutes with 700 lines as it is.

Thanks for the info.

Scott, LMS

Scott,

If you let us know your email address we'll send you the article as it's no longer available on the MS Site

The Sprezzatura Group

World leaders in all things RevSoft

View this thread on the forum...