>>Hi,
>>
>>I have come across the following problem.
>>
>>I have the following segment in a SQL Select:
>>
>>select RF_FILE.RISK_FACT, EQ_FILE*. FROM EQ_FILE JOIN RF_FILE ON RF_FILE.RF_PK = EQ_FILE.RF_PK
>>
>>
>>In SQL Server, because the field RISK_FACT appears before the EQ_FILE*., the column RISK_FACT is selected from the RF_FILE. But when using a VFP database, the SQL Select gets two fields RISK_FACT_A and RISK_FACT_B, one from each table.
>>
>>So, the SQL Server works as I want it. But with VFP database, it does not work.
>
>On the contrary, the VFP does work as it should. You specified two fields with the same name from two tables, you should get two fields with some way to resolve the ambiguity. Probably the SQL does it too, but uses a different renaming scheme.
Thank you.
"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
