>>>>Hi,
>>>>
>>>>When executing a long SQL Select command I get error "Invalid column name 'GROUP_ID'". I do have the very first column of the SQL Select defined as "MYFIELD AS GROUP_ID" and then I have GROUP BY GROUP_ID at the end of the SQL Select.
>>>>
>>>>Is GROUP_ID a reserved word?
>>>
>>>No, AFAIK, but you can not ORDER BY the new field. You should ORDER BY the original field, e.g.
>>>
>>>
>>>select myField as Group_ID from myTable ORDER BY myField
>>>
>>>Obect_ID is a SQL Server function.
>>
>>I verified that the name of the field is not the problem (I changed it and get the same result). But I am a little confused by what you are saying. I get error on 'GROUP BY" and you are referring to "ORDER BY". What am I missing?
>
>I didn't notice you were talking about GROUP BY, but the same rule applies. Use the actual field name, not the new name.
>
>Can you post your statement, so I can help?
>
>BTW, I mistyped. It's Object_ID. My son who was standing near by told me, but I already switched to my gmail and didn't re-check as usual my message.
You were so eager to get your stars that you didn't have to read my message :). My SQL Select is very long and I am not sure how it would help. This statement works very well against VFP data but now I am testing it against SQL Server and get this error. I am thinking that maybe SQL Server wants the statement to have ORDER BY first and then GROUP BY. I will test it now.
"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