>>>>Yeah, but in the old days, 'Select A', 'Select B' was about all we had.
>>>
>>>Many years ago I took over a dBase III project where the previous programmer had named his files A.DBF, B.DBF, etc.
>>>
>>>Worked fine as long as he opened A.DBF in A, B.DBF in B, but otherwise it caused the most AMAZING errors :-)
>>>
>>>Barbara
>>
>>Oh, I'm sorry......don't things like that just make you wanna go FIND the last programmer that worked on the project and......hurt them in new and imaginative ways?
>
>Since the fields often had identical names (like DATE, DESC, and (really!) MEMO) the code was --- ummm --- interesting.
>
>Barbara

"Interesting"?? Yeah, I suppose that's ONE word that could be used. I'm currently having to deal with a system whose PROC file is called 'library'. When the contractor was informed that that was a reserved word in Fox, he said he didn't want to change the name because "he didn't want to have to change it everywhere else it was used". Sure enough, he was setting the proc file EVERYWHERE (!)......along with closing the database and reopening it on the next line, #include-ing his 'constant.h' at the top of every method, program, function, procedure. It's been way too much fun trying to support this thing.