>Can anyone please help with these questions:
>I have used the Oracle upsizing wizard...
>The tables go over, the index go over and so does all the
>relationships....
>The wizard renames the local tables as *****_local.
>
>1) How do i get my application to point at the tables on the
>Oracle Server and not at the local tables...
>
>2) How does Oracle look at the indexes? The same as VFP does
>do I have to re-do my application?

These are some big design questions so anything I say here has to be qualified. A lot depends on the size of the tables and the nature of your application. With that in mind, the easiest way to get your application to point at the Oracle tables is by using remote views. Create a database (dbc) to contain your views, create a connection to connect with Oracle and the create remote views to your data. With a little care, you should be able to make the views look exactly like the FoxPro tables they are replacing.

The indexes in Oracle are used for optimizing record retrieval or, in the case of a primary key, for data integrity. They are not used for ordering records. The 'order by' clause in your remote view will have to do that. When indexing, use the same rules in Oracle as you would use for using Rushmore optimization in FoxPro. Primary keys in Oracle are self-incrementing. So, once you define a primary key on a table in Oracle, Oracle itself keeps track of it. You won't even see it.

As far as what you will have to re-do in you application, a lot depends. The better you can keep the data separate from the interface in your application, the easier it will be to move it from one data source to another.

I hope this helps.

Gregg