>Mark,
>
>Again thank you very much for your input. If we use the Personal Oracle for development for the back end tables, do you foresee any difficulty keeping the individual Oracle tables synched up? I probably will have people in remote sites also assisting in development, so in the event a structure change occurs I'll need to easily change structure to ensure "version" control.
>
>Does the Personal Oracle support remote views and "upsizing" from VFP?
>
>I have used your ODBC class in other programs and it works like a champ. Again, Thanks a lot.
>
>Wayne Frenck

Personal Oracle is exactly like the real deal. You must keep track of any changes you make in the development database. Once your production DB is running, you will have to make these changes mostly manually. These is not a tool like SDT to handle Oracle-side changes.

You can put all those changes into a PRG and use SPT to update the Oracle DB and provide the FXP to your customer. You can make your application smart enough to detect this FXP and automatically run once to update the DB then delete it after it runs.

I would also design the APP so it will not run until the FXP update runs and disappears.

This is also where a LAUNCHER app comes in handy. My Launcher EXE looks for an updated APP on the server. If it finds one, it copies it to the app's installation folder. At the end, launcher issues a DO ("MYAPP.APP") I use that syntax to fool the Project Mgr so MYAPP.APP is not added to the project.

The launcher can also look for the Oracle update FXP and run it before starting your app.