>>>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.
This is what pretty much I did; cut/commented the number of fields in half; then another half and so on. It only took me about 2-3 minutes to find the "offending" field. It would be nice, however, if SQL Server error message was more detailed.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
