After executing the popup, I have tried conducting a search for a particular string and each time I receive the following error : "Popup has reached the maximum allowable size for your memory configuration".

I have checked the settings on my shortcut (Windows 95) and have set all of the memory allocations to auto. Do I need to set the configurations for something other than that or is it just simply a case of the popup being too large ? Is there something that I need to do via AREV to increase the memory allocation ?

I am trying to avoid changing the popup, ie, making it more specific or parcing the data into a couple of different styles. I'm sure we could give the user an option to choose customers from A to G and so on but we also don't want to rock the boat too much.

Any advice will be greatly appreciated.

Thanks,

André

Once you get more than 64 kB of data, a popup is not really that workable. There may be a couple of options.

(a) as you suggest, split the selection into two popups/phases

(b) reducing the physical size of the data you have in columns 2+

© reduce the width of columns

(d) write a routine where you key selection criteria into a message first, then have it display a subset (like (a) above but using MSG)

(e) write a select with the first X,000 records in it, and use this to populate the popup partially.

Steve

Steve, of course, is right about the problem being that your popup data has reached the 64K limit. Depending on how you're feeding it, if you're using BTREE.EXTRACT, then you can use the OVER 64K flag and display chunks of data in a popup, then when the user escapes, if there's more, ask if they want to see the 'N'ext or 'P'revious chunk.

Of course, you would keep track of whether you're at either end and not ask the associated non-question of 'N'ext (if you're at the end) or 'P'revious if you're at the start.

Of course, BTREE.EXTRACT will tell you if you have ] 64K in KEYS, not data, so you have do experiment and find out how many keys, max, you can display in one popup and only use that many, caching the rest in the calling program.

Other that, if Steve's suggestions about reducing display size aren't enough (and they usually won't be if your data file is expanding)you're SOL. 64K is an unbreachable limit in AREV. (unless you run the old OS/2 version on OS/2).

Larry Wilson

[email protected]

I have several popup producing programs that have the potential to go oversize. There are at elast two things that can be done. The 1st is to simply monitor the size of whatever variable you are using for DISPLAY. If get to larger than 65000 characters, then put up a message and ask the user to refine their search parameters.

The second thing to do is to give the users enough parameters that they can refine the search to a usable result set.

View this thread on the forum...