The ODBC driver I am trying to use is the one that comes with Visual Foxpro.

The syntax ofthe SQL startement is dead simple:
select part from prd where serial='10010023'
This should return 'FUX13E'.

I have set up a Data source to a VFP database called rawdata. There is a table called prd in it.
There are a number of fields, of which part and serial are two.
According to all of the documentation that i could find with VFP, the driver should support this syntax.

Thanks for all of your help,
Mike

>Have you verified that the ODBC driver supports the syntax you are attempting to use? Can you post the SQL statement for us to review?
>
>Dan
>
>>The select I run inside fox, returns data... yet the same one from another application (InterSock) returns nothing..
>>
>>I turned on SQL tracking and here is a snippet from that log.
>>
>>InterSock fff60c2d:fff739a1 ENTER SQLFetch
>> HSTMT 0x008d0ba0
>>
>>InterSock fff60c2d:fff739a1 EXIT SQLFetch with return code 1 (SQL_SUCCESS_WITH_INFO)
>> HSTMT 0x008d0ba0
>>
>> DIAG [01S01] [Microsoft][ODBC Visual FoxPro Driver]Error in row (0)
>>
>> DIAG [01004] [Microsoft][ODBC Visual FoxPro Driver]Error: Column 1 ( part ) (0)
>>
>>I have used the same software to query tables in an Sybase database using the SQLAnyWhere ODBC drivers and it returns the data (or no data as the case may be) see below.
>>
>>InterSock fff60c2d:fff739a1 ENTER SQLFetch
>> HSTMT 0x008d0ba0
>>
>>InterSock fff60c2d:fff739a1 EXIT SQLFetch with return code 100 (SQL_NO_DATA_FOUND)
>> HSTMT 0x008d0ba0
>>
>>Any ideas what is going on?
>>
>>
>>I would hate for this to be a stumbling block for the Fox.. i.e. if Fox cannot do it, I may have to switch to PowerBuilder application development. Just so I can do the above.
>>
>>
>>Also, the command takes a long time to execute.
>>
>>TIA,
>>Mike