Trying to read data from a Dbase to an AREV file, the KEY to the records is 20 characters in length, each record is approx 220 bytes.

We read the record from the dbase file and then write a record to the arev file. After 3120 records are written the arev file breaks with the message of:

Fatal error writing 10000000000000000001 in file XYZ. The total length of all the key ids in the group exceeds the maximum variable length.

Doing a Dump shows a Group Modulo of 2, Framesize=1024, Size lock=0

All records are in group 1, if we change the threshold and then compress the file, records are placed in many groups. At this point we can write as many records to the file as we want… it appears to be fixed.

You probably have a quickdex or rightdex on the ARev file.

According to my calculations, 3120 records, at 21 bytes per key (20 for key length + 1 for delimiter) equals 65520 bytes, which is over the 64k max in ARev.

If you remove the quickdex or rightdex, your problem should go away. To remove quickdex or rightdex, type "DICT " from the TCL. Then, press to see a list of options. In ARev 3.02, you press to add/remove a quickdex/rightdex on the data table.

When you hit , or whatever the shortcut key is, the system will ask if you want to delete the quickdex/rightdex. Say Yes.

The reason this is a problem is that a quickdex/rightdex is stored as a record in the dictionary of the table, and the keys are stored in an appropriate sort. If the total length of your keys (plus delimiters) is greater the 64k, then the record cannot be written to the dictionary.

HTH,

msorrel@greyhound.com

Greyhound Lines, Inc.

And then I re-read the post and realized that it's maybe not a quickdex/rightdex issue.

I honestly have never seen this before.

msorrel@greyhound.com

Greyhound Lines, Inc.

I am sorry, I have answered/asked in the other thread.

It is bad joke to start two threads with the same topics.

(I did it at least once, too :))

View this thread on the forum...