>Any tips or problems to watch for whenr upsizing
>to Oracle using VFP6.

Since there wasn't another reply to your question,
I'll give a general answer from my experience with
upsizing to MS SQL Server (I've never upsized to
Oracle although I use Oracle).

The upsize wizard doesn't always do a good job
of complex table layouts. The wizard sometimes
leaves out the relationships totally when the
chain of the tables gets too long.

Write extremely generic field level Update\Insert
triggers that you have tested in Oracle\SQL Server.
If they are not extremely generic, the whole trigger
gets left out. As an example, a good upsizing
trigger is:
myfield<>" "
while the following won't be upsized:
LEN(TRIM(myfield))<>0

The upsizing of field "defaults" seems to work
flawlessly!!! This really saves time!!!

VFP produces a great dbf that shows the problems
that were encounted during upsizing in the
"c:\Program Files\DevStudio\VFP\Upsize" directory.
The upsize wizard is just fantastic!!! Saves a
great deal of time and effort.

Do not upsize data at the same time you upsize
the tables. Generate the script from Oracle/SQL Server
that the VFP Upsizing Wizard produced and do
your own modifications to the Oracle/SQL Server script.
Delete the database from Oracle/SQL Server and run
your modified script to recreate the database, tables,
triggers, etc.

A special note: Review the Oracle/SQL Server generated
script line by line. Don't assume because something
is "not complicated" or "it upsized on one table so it
must have upsized on another table" is always the case.

Other areas that the upsizer had problems with in SQL Server
(I know you asked about Oracle but perhaps this will give
you insight):
- Indexes: All primary keys are created clustered. Easy to
fix but a pain in the neck since most tables aren't clustered.
- Indexes: Some indexes where just not created.
- Deletes: I never have gotten cascading deletes to upsize.
(Does anyone have a solution?)

I really want to stress that although the upsizer isn't perfect,
it is still fantastic. On a fairly complicated database layout,
the upsiser will save around 50% of your developement time.