Tried the MS Oracle drivers. It says I have no "client software." Downloading Personal Oralce for the heck of it. Good thing I have a high-speed line and a big hard drive. ;-) I don't think using MS drivers will get me anywhere. It's like hoping they speak Portugese in Spain because they're both in Iberia.

Again, this product was originally developed by Digital Equipemnt. It doesn't use PL/SQL for example.

In any case, the syntax I'm using to test is "SELECT * FROM Locations" where Locations is a nice little 20 record file. I've also used "SELECT Location, Title, Active_flag FROM Locations" with similar bad luck. Definitely not complicated syntax!


>>Don't forget, it's NOT "regular" Oracle, but a little-supported stepchild. I sincerely doubt there are MS drivers.
>
>Yeah, I say that. I have no idea what the difference is between that and regular Oracle. You probably already have the MS drivers installed and you have nothing to lose by trying them.
>
>>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.)
>
>Not necessarily. Access has different native SQL syntax for querying their own data. If querying a remote data source. The drivers convert Access syntax to the syntax of that source. e.g., Access used to [still does?] use the asterisk instead of the percent sign. The drivers corerctly interpret the Access syntax but not VFP syntax.
>
>I would think that since this is still an Oracle product, they would still use the same SQL syntax as they do in the regular Oracle. We do know that VFP SQL syntax is interpretted correctly by the MS ODBC drivers for Oracle.
>
>>I've connected with SQLConnect() and SQLStringConnect(), and then retrieved data with SQLExec()