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
Determine the architecture
Software architecture is about the pieces and how they connect. It includes the major choices of tools, such as the language or database system to use, and whether it is a web, desktop, or mobile application. There is often more than one architecture that would meet the requirements, so the best choice is usually the simplest one. The architecture of most projects can be explained and diagrammed on one page.
Basic questions answered by architectural choices
The architecture should answer these questions:
If you already know that you will be using Axisebase without any programming, then your architectural choices boil down to one main question: where the database is hosted - either in house or at an ISP.
Here are two examples of architecture choices for a software project:
1. In-house with public web access
2. Database and web hosted by separate ISPs
Multiple databases with Axisbase
There are several cases where you might want to use more than one database file. Axisbase supports this by linking files together so you can use all the data and building blocks in one file from another file.