>>Or else they have fixed the "file not found" which never tells you which file was it. It's unchanged since 1981 or thereabouts. This immediate amnesia, where the code immediately forgets which file/field/routine caused the error, is a long standing feature which will live longer than we do.
>
>I agree that "fine not found" is very annoying message; to say the least.

All such messages are highly irritating. Your database tool doesn't know which field it was doing when the error happened? I'm seriously underwhelmed (well nobody gets whelmed right, for that matter).

>I had to find the "offending" field using the old-fashioned method of commenting one or two fields at a time.

When it's one among few dozen (and I've had up to 120 sometimes), binary search does it. Comment the first half, give it a try. If it still breaks, uncomment that and comment half of the other half, or else uncomment half of that first half. Much faster than eyeballing.