>>>Where did I say they are not reserved words?
>>>I was not discussing "using reserved words" but "using one letter aliases in SQL statements".
>>
>>While you may not be "discussing it", a single letter alias of A-J and M fit in the category of a reserved word. Kind of like trying to use a field name like "DESC" in a SQL statement. While that may or may not always cause a problem, I have seen VFP have problems there, too. Patient: "Doctor, it hurts when I do this." Doctor: "Don't do that." ;)
>>
>
>This reminds me of a stand-up comedy with a student trying to pass the biology exam only knowing about the cucumber. Every time he was asked about another plant, he'll say "[plant name] is a plant unlike the cucumber, which [keep talking about the cucumber]..."


I really do fail to see how it is not a reserved word situation. While not all reserved words will cause problems in all situations, there are definitely places it can burn you. This used to certainly be one of them. If it's fixed, great. Feel free to use single character aliases in SELECT statements, however, I still will not, if for no other reason than lack of clarity.


>>>So you qualify "problems in the past", "things that could potentially cause problems", "past issues" as facts? To me they look more as FUD than facts. If you have any facts, i.e. reproducible problems, with code samples, I'd really want to see that.
>>
>>Since even Tamar (one of the authors of "Hacker's Guide") has said that there *were* problems, and I can't recall which version it was (one that I'm most certainly no longer using), why should I dig up an example? I don't use single character aliases. Period.
>>
>
>Well, I also have the Hacker's Guide with Tamar & Ted testimony, but there is no code sample either, IOW no facts. I guess you suggest I should look at this like some kind of religious belief.
>

You won't get any religious arguments out of me, I side with Dragan on those issues. <g>

I no longer use the versions of VFP where this was a problem, I haven't even tried to use a single character alias in a SELECT statement in ages, so why would I even attempt to recreate the problem? It CAN'T have any impact on me because of the way I now code SELECT statements. If I recall correctly, it wasn't a failure that occured everytime, anyways. All I know is when I changed from using them, I no longer experienced any problem, whether the VFP team fixed the problem or not.


>>>You are back to "using reserved words" issue - it is another topic, I'm not debating that, and never did in this thread.
>>
>>As I said, feel free to carry on. I'm not debating the issue either. Not sure why you insist on doing it.
>
>Because I was hoping to get technical advice from you.

I've given my opinion on using a reserved word. You don't seem to agree that it is, so I can't give you any advice since we don't agree on terms.