VFP may not recognize Oracle indexes, but the SQL VFP passes to the Oracle DB definitely makes use of those indexes [actually Oracle makes use of them after receiving the SQL command]. The better your indexing scheme on the Oracle side the faster your queries, remote views, etc., will perform. Just make sure any fields you are doing joins on are properly indexed on the Oracle side. Index optimation rules you would follow in VFP still apply to Oracle indexing.

Your observations of 80 to 100 seconds is indicative of a problem with indexing or non-optimized SQL. I routinely query 1 million record Oracle tables with return times usually less than 10 seconds. I am also using the MS ODBC drivers.

So, there is hope for you. The problem is pinpointing the real problem.

>I am retrieving both tables and views from Oracle (VFP will not recognize my index keys when I select then into a remote view, thus making joins very hard to do). I had turned off autoarchive, but then ran out of space on the archive log ( Connection Error: End of file encountered) which crashed my import. At present, I am trying once again to finish the import. A select statement within a loop on an oracle base table is averaging 82.34 seconds, and reaching over 100 seconds. The query is mereley maing certain that the record is not already in the table
>
>select sernum from pers where pers.sernum = m.sernum into array temp;
>if _tally <> 0
>yadda yadda
>
>So, speed is a vey major concern. I am using the "latest and greatest" driver, the one supplied with Oracle 8.0.5.