One of the tables in an application I support is getting dangerously near the 64K limit for a Quickdex that a previous programmer put on it. I would just remove it, but I'm afraid I might break some code written expecting it.

If I remove the quickdex and put a btree index on the key field will everything work the same? Is there some way other than using a quickdex/rightdex to get the table to automatically list in key order?

Jim [email protected]

I don't know of any way to automatically get your file to list in key order except with an MFS. Instead of a BTREE, I would suggest writing your own MFS that feeds SELECT calls (resolved or not) a

SSELECT. All other codes of that MFS would just dump the MFS and call the next MFS (probably RTP57). If you need some help with that,

visit my web site at:

http://members.tripod.com/rehabsw and go to the AREV forum. It would be an interesting exercise, and we could post the MFS on the site when done (there are lots of folks who would gladly help).

Other than that, the only thing I know is to put a sort into every pop-up that calls that file and make sure all programs that need the IDs in order do a SSELECT first (either PERFORM or extended SELECT).

Hope that helps.

Larry Wilson

TARDIS Systems, Inc.

[email protected]

303-680-8555

To list your file in record key order, modify the default dictionary group @CRT. ie. DICT filename @CRT.

In the group phrase, type: LIST filename by @ID

(You can replace @ID with the actual dictionary name for your key field to insure right or left sort justification.)

Never put a QUICKDEX on a datafile.

The @CRT phrase should be: BY @ID

AT tcl type: LIST filename

While the two replies about @CRT are essentially correct, they do not provide the pre-sort properties of %RECORDS% that QUICK/RIGHTDEX except when doing a list from TCL or a report that has no other parameters than LIST Filename. Any other parameters render @CRT unused. If @ID could replace the DEXes, RTI would not have put it them in place. I assumed (correctly I think) that you were looking for pre-sort functionality when doing a 'select filevar' in R/Basic or when popping up a list of items without a preselect, etc., etc.

Larry

]Never put QUICKDEX on a datafile.

What not even a small (relatively) static lookup table like state abbreviations or company codes (multi-company corporation)?

Now we get into the intersting world of semantics. I personally do not consider lookup files to be datafiles per se and thus have no problem with denormalising them!

Thus the original statement by whoever would still stand as the examples you give are lookups designed to translate a code into a description.

[email protected]

Sprezzatura Ltd

World Leaders in all things RevSoft

([email protected] onmouseover=window.status=why not click here to send me email? return(true)", Sprezzatura Ltd)

([email protected] onmouseover=window.status=why not click here to send me email?

return(true)", Sprezzatura Ltd)

View this thread on the forum...