The database must be defined via the RDBMS database/schema definition facilities. In SQL-Server this would be SQL Enterprise Manager. You should define a database space of at least 20MB for the distributed sample data, more if space permits.
As supplied the VisualInterdev project includes a complete data project corresponding to the latest release of the generic E-Catalog.
An ODBC DSN ``XASPAPPDB'' or ``XASPAPPDB2'' is assumed by the web app and this should be created either from the ControlPanel or in VI. The 2 names correspond to ``ECatalog'' and ``ECatalog2'' as described below.
It should in principle be possible to initialize the database schema using the Data View in VisualInterdev. However I do not recommend this, you should instead use the file ``ecatddl.sql'' supplied with the AnyFront utility to define the generic schema.
We use the names ``ECatalog'' and ``ECatalog2'' for the database switching the two between test and production roles. Once the database has been created on it's serving host, adjust the elements in the Data View in the VI project and in the E-Catalog element under global.asa in the Project Explorer view to the database names you actually use. Note that just changing the name/ODBC DSN is not enough, you need to go to the ``Miscelaneous'' tab and set the database name there as well.
The Data view is the place to adjust constraints, indices and other elements which are not addressed by AnyFront.
The remainder of this chapter should be skipped on a first reading.