Run the Application on a Different Database
If you created the Sales Entry Application on a test database and want to run it on a production database, you can do this in either of the ways described below.
In the first method, the Sales Entry Application remains in the test database in which you developed it (Testdb) and created an executable image (sales.exe).
To use this application on the Proddb database, make sure that all the components in the application--forms, reports and tables--exist in the production database (Proddb). Execute the following command at the operating system level:
Windows: Create a shortcut to the following command:
full_pathname\sales.exe -dproddb
UNIX:
alias saleapp
full_pathname/sales.exe –dproddb
VMS:
saleapp :== "$dir_spec sales.exe-dproddb"
Users can execute saleapp or sales (Microsoft Windows) to run the Sales Entry Application in the Proddb database, while the definition of the Sales Entry Application resides in the Testdb database.
As an alternate approach, copy the entire application from the Testdb database to the Proddb database using the copyapp utility, discussed in the section, Copying an Application into a Different Database. Then build a new executable image in the Proddb database.