>
>1. Error 114 (Index does not match table) starts cropping up.
>2. Geo (that's me) implements a localized error handler (very OOP like design in a non-OOP environment, IMHO BTW). Anyway, it deletes the CDX and retries the command to open the table. This should generate error 1707 (Structural CDX not found). Which will be passed onto the general error handler, which, in turn should rebuild the index. All's right with the world, except...
>3. Now error 1113 (File Not Open) starts popping up. After messing around for most of the morning (not being able to open the file either in FPW or VFP), I find that if I delete the CDX, the file will open.
>4. I modify the localized error handler, to handle this, but...
>5. When the RETRY is issued after error 1113, the error handler is again tripped by the line of code. This time, however, ERROR() returns 0, but MESSAGE() returns "Structural CDX not found." This gets passed onto the general error handler. Since 0 isn't accounted for, the code simply shuts everything down, and logs the message.
>
>Geez, it's been 30 years since I made a living flipping burgers...

Maybe pancakes is a better opportunity today... well, it depends on your market, and ain't much compatible with beer.

"File not open" always was a weird error message, and (in the old days, when we started using FP and networks were just couple of cables) meant that you've opened a file on a floppy and then took the floppy out, or that your cable to the server went hanging around. Are you sure your table ain't just toooo big for your network client, quotas, or maybe your connection just times out etc? Just ask your NW guys/gurus what's your client's capacities, since it seems it can't read the .cdx properly. It may be something just as simple as having run out of free handles (and can't resort to using legles, or whatever is the corresponding item in hand->handle, leg->?).

As for the error handler returning a wrong error number... well, I've seen worse things in these situations, when you rely too much on repeated error handling - it loses breath too soon. Ever tried to type in the command window while there's a suspended error handler? In FP1.0x it stopped checking syntax altogether, and let you type any idiocy you like. As they say, "nobody's perfetc".

p.s. if you need a recipy for æevapèiæi (Serbian version of kebab) or sarma (minced meat rolled in sour cabbage leaves), let me know.