You can run your application on a different database from the one in which you created it by defining a special command. This feature is useful when you must develop an application on a test database and later run the application 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 database in which you developed it. You developed the Sales Entry Application on the test database (Testdb) and created an executable image (sales.exe). Testdb is the only database containing a definition of the Sales Entry Application.

To use the Sales Entry Application on the Proddb database, make sure that all the components in the application—forms, reports and tables—also exist in the production database (Proddb). If the forms of the Sales Entry Application have been linked into the application image, it is not necessary to copy the forms. Reports are never linked in, and so must always be copied. Perform the following instruction that applies to your operating system:

Windows: Make a shortcut called salesapp to the following command:

UNIX: Execute the following command at your operating system level:

VMS: Execute the following command at your operating system level:

After this, users can execute salesapp to run the Sales application in the Proddb database, even though the definition of the Sales 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. Then build a new executable image in the Proddb database.