Don't forget, it's NOT "regular" Oracle, but a little-supported stepchild. I sincerely doubt there are MS drivers.

Wouldn't the drivers be Ok if I can retrieve data correctly with Access and MS Query, or is it possible that they can work with two front ends and not the third? (BTW, no one else is using W2000 yet, and everyone else uses Access as a front end.)

I've connected with SQLConnect() and SQLStringConnect(), and then retrieved data with SQLExec()


>You have probably figured out the problem -- the Oracle drivers are probably to blame. If so, there is not anything I know of you can do to fix it. Obviously the problem is not with SQL*Net or your host file [tnsnames.ora] since Excel and Access work. Can you try using the MS ODBC Driver for Oracle?
>
>How are you connecting? SQLExec? SQLStringConnect? RV? With or without a DSN?
>
>>I'm having a problem with Oracle Rdb ODBC and VFP6/7. I thought I'd bounce it off a few people before I call MS for support.
>>
>>Please understand that this is NOT "regular" Oracle, but a "stepchild" they bought from Digital Equipment that doesn't get a lot of support. The database is a large decision support database of management data I query often, but never write to.
>>
>>I am able to successfully access this database with an older set of ODBC drivers under W98. When I rebuilt my home machine to W2000 I got a new set of drivers and began having problems retrieving data.
>>
>>MS Access and MS Query (through Excel) work properly, but when I retrieve data through VFP I do not get any field names, only Exp, Exp1, etc. and the data types are wrong, with dates and SUM() fields coming through as text. The data, as far as I can tell, are correct.
>>
>>My guess is that VFP cannot properly communicate with this ODBC driver. Anyone seen anything like this before?