Home Evaluation Summary for programmers Product limitations Goals of Axisbase Quick start Installation Using the launchpad and opening databases Connecting to a sample database Using building blocks Planning Define the purpose Define the requirements Borrow existing work Determine the architecture Design the data model Design the process model Deploy and maintain the product
building blocksPerforming a mailmerge Bulk e-mailing
ProgrammingSingle-threaded progress indicator in c#
Database menu itemsImport XML Save Copy As Integrity Check Change Password
Database Properties windowOpening the database properties window Record types tab Display types tab Roles and Users tabs Sidebar tab Database ID/Links tab Counters tab
Building blocksBuilding blocks window Editing grids and cells Hyperlinks and nesting Data Subset window Data Outsource window List window Window window Report window Bulk Operation window Label Printer window Choosing a data source
Special topicsExpression syntax Browse records Storing building blocks within other building blocks Programming Using custom code in building blocks Using Axisbase as an embedded database Axis1.Util namespace reference Axis1.Data namespace reference (Fishnets) Axis1.Data namespace reference (other) Axis1.Forms namespace reference
Define the purpose
Is this product for your customers to use? Are you tracking data to meet compliance rules for a government agency? What do you need to get out of the system years from now?
If you are working in a team, write down the purpose and agree to it no matter how simple it is.
Consider the following two versions of a purpose statement.
The system will track warehouse inventory, so that we know how much of each item we have on hand and how much is on order. We need to allow customers to check inventory from our web site.
The system will manage warehouse inventory so that we will have enough of each item on hand to make deliveries.
The second project is potentially more extensive than the first. It suggests that the system might order from suppliers automatically, and it might predict demand. That is a lot more than simply tracking inventory. The second purpose statement should be expanded to name the various roles that the planned system will play.