The first lesson describes how to set up the project architecture and creating an UltraLite database for the tutorial.
Create a directory for this tutorial.
This tutorial assumes the directory is c:\Tutorial\mbus. If you create a directory with a different name, use that directory throughout the tutorial.
Create the following subdirectories for platform-specific files:
Configure your web server:
Map a virtual directory named tutorial on your web server to c:\Tutorial\mbus. The URL to access this directory will be http://localhost/tutorial.
For Microsoft IIS, you can make these changes from the management tool.
For Apache, make a symbolic link named tutorial from your document root to the c:\Tutorial\mbus directory, or copy the tutorial files into your Apache document root.
Ensure that your web server delivers the following files with MIME type application/octet-stream:
For Microsoft IIS, you can make these changes from the management tool. Go to the virtual directory properties and make the changes under HTTP Headers and File Types.
For Apache, edit the file mime.types in your conf directory.
Create a database using UltraLite in Sybase Central.
For more information about creating a database, see Creating an UltraLite database from Sybase Central.
Table name Customer
Columns in Customer
|Column Name||Data Type (Size)||Column allows NULL values?||Default value|
Primary key Ascending ID
Save the database.
If you are developing an application for Windows or Windows CE, choose File > Save and choose tutcustomer.udb in the WINCE_OS or the WIN32_OS subdirectory of your tutorial directory as the file name.
If you are developing an application for Palm OS:
From the File menu, choose Export Schema for Palm.
Enter Syb3 as the creator ID.
Save the file as tutcustomer.pdb in the PALM_OS subdirectory of your tutorial directory.
A note on Palm creator IDs
The creator ID is assigned to you by Palm. You can use Syb3 as your creator ID when you make sample applications. However, when you create a commercial application, you should use your own creator ID.
If you are developing a cross-platform application, save the database file in all the above locations.