>We are in a long term project converting from Fox to .NET. Right now in stage 1 we are switching over to CursorAdapters, streamlining code, establishing hard boundaries between UI, middle and back-end, and really trying to push toward a 100% data driven package for stage 2. Stage 2 which is hook to Sql Server, then stage 3 convert to .NET front and middle.
>
>Well, our sales guys are asking about Oracle instead of Sql Server for stage 2. Outside of the cost to obtain Oracle any opinions to which is better, translates better, easier, more scalable? On a scale of 1 to 10 we are about 4 to a 6 on Sql Server and a 1 on Oracle.
>
>One thing is that we build queries and view definitions at runtime and do not store any procedures other than ri code. We know that some stuff ( statis functions etc... ) will have to be converted to stored procs but we still need to ability to build queries/views at runtime since we dynamically allows users to add/drop columns viewed in grids/forms. We also allow users to add user defined columns at runtime ( basically modify the fox db through a form we built ).
>
>Thanks.

I didn't know much Oracle but I have experience with SQL Server, so I can't tell you which one is better. One of the Oracle advantage is that it could be installed on every OS, SQL Server requires only MS Windows.

All things you want, adding columns at a run time, build dynamic queries could be done with VFP no matter what Backend Database is.
As I said, this is only my opinion.