Thanks Sergey.

Unfortunately that won't be an advantage here, as the author, in some 100 .prgs, foolishly selects specific work areas all over the place, rather than 0. So any slected area (even when selected 0) may be overwritten. That's why I needed the u/t, to check whether or not he's used 25.

>You can get the highest available work area with ? SELECT(1). It'll be either 25 or 224 depending what rintime is used (extended or not).

Now in native fpd2.6 the highest selectable is 25. If build exe with the extended checkbox we can select up to 224 then? As I thought.

>
>>I've go a dilemma in that looking at some old rubbish code (FPD26), tables are continually opened in specified work areas and closed. Now there's a table that I need to ensure I keep open throughout the app. I do:
>>
>>Select 0
>>Use DefDirs
>>
>>But 0 returns 1, as this is the first table oppened. Within a heartbeat there is code to:
>>
>>Select 1
>>Use Whatever
>>
>>and this happens (1 used) throughout this sorry suite of code.
>>
>>So it looks like my only recourse is to open DefDirs in a numbered area that won't get re-used.
>>
>>Now AFAIK you can only use 25 work areas in FPD26. I was thinking of opening DefDirs in 25. But I need to check through this labyrynth of progs to check that 25 (or whatever) isn't used somewhere else (for the same lame reason).
>>
>>Anyone know of a readily-available tool that can search a bunch of files for a specific string?
>>
>>'ppreciate it
>>
>>Terry