Segment lengths do not match

[Walter Vaughan]

AIT - Mark Comins wrote:
> Jaime,
> I have tried the following with limited sucess.  Cd to the directory and 
> mv key savkey
> mv data savdata
> cp savkey key
> cp savdata data
> 
> By moving you are able to keep the data on the same part of the hard 
> drive.  Copying back makes a copy of the file to another part of the 
> hard drive that might not be bad.  If the copy is sucessful then chown 
> the two new files to filepro and try and go into IUA.  If you still et 
> the segment lenth error - try adding one record in expand records.

That sounds like such a bad idea on so many levels. I'm kinda surprised no one
else chimed in yet....

First you really got to figure out why the OS is telling filePro that the
lenghts are not what filePro expects. You gotta do some math (don't forget about
20 bytes per record on the key segment), and you will use completely different
methodologies if it's due to an interrupted expand files, or if the data or key
segment got truncated, or some other reason. You gotta figure out if/where the
segments are no longer coherent before making it much worse.

Just copying or trying to add a record should NEVER work in my opinion, but if
it did for you once, then that's great, but I would never trust that table again.

This is the kind of problem that should never happen today; key/data segments
are a throwback to an time long, long ago. A time of diskette based systems and
  "Welcome Back Kotter".

If the data is valuable, it should be on a RAID array. Any speed improvents that
a key/data segment structure will be lost in the overhead of two calls for data
rather than one. Moving tables back to a zero lenght data segment are PITA, but
doable. I kinda remember someone had a utility that did migrate information in
the data segment and moved it to the key segment.

--
Walter