You must deploy a database along with your application files.

While building a Web application, many UltraDev developers work with a prototype database located on a local desktop computer or on an in-house server. The prototype database may also contain prototype data, not real data. Before deploying such a database, remove all prototype data, enter any initial data, and fill out any lookup tables. (A lookup table is one used primarily for reference purposes, such as a rate schedule.)

Another option is to create a new database. If you do so, make sure the structure of the new database is identical to the structure of your test database. For example, in the new database the number of tables and table columns—and their names—must match those in the prototype database.

How and where you deploy the database depends on a number of factors. For example, if you have a file-based database like Microsoft Access, you might use UltraDev to upload the file to the host server along with the rest of your application files. On the other hand, if your database is a server-based one, then you might decide to "deploy" it by establishing a network connection between the database server and your application's host server.

Once the database is deployed, the next step is to modify any database connections to it so that the pages of your application can still find and interact with it. The topic is discussed in the next two sections.