Does anyone remember a limit on the older ARev version's, specifically 1.16, where they would only save about 32kb in the rightDex or LeftDex index?

I have a system that seems to be doing this. I do not have access to the source code so I cannot correct the programs behavior.

Any thoughts would be welcome

Paul,

Quickdex/Rightdex indexes are stored in the dictionary of the table as a single entry and as such can store up to 64k if keys.

John

J.C. Henry & Co

There are two Quickdex / Rightdex options: Data and Dictionaries. In versions of AREV prior to 2.x, I think there was a 32K limitation at some point which was corrected to 64K in a maintenance fix. Version 1.12 used to have this, I think. In any case, the keys were stored in a system record %RECORDS% in either the DICT. or in itself. Sometimes this used to cause a problem when doing record counts. Again, my best recollection is that it was fixed with a maintenance release to 1.x and in 2.03. Assuming a 5-byte key with a @VM separator, the limit was around 10,000-11,000 keys in %RECORDS%. If the file was at all large this could cause problems when saving a record due to key overflow. Also, the RIGHTDEX option could take some time in adding / deleting records given the use of the LOCATE BY function to insert or find the key.

I don't think the source to the MFS was ever released. HTH…

Don Miller

C3 Inc.

That is what I remembered also. Could be that was part of the fix in 1.16. Wouldn't have any idea how I could get ahold of those old upgrades?

At least part of my memory worked. Now if I could just get the source so I could upgrade them to a newer ARev version.

Thanks

You might try RTI Customer care - but all things being equal, I tend to doubt it's availability. Another possibility is Sprezzatura since they have a giant trash bin that doesn't seem to empty all that frequently .

Cheers..

Don Miller

C3 Inc.

View this thread on the forum...