Documentation
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
Tutorials
building blocks
Performing a mailmerge
Bulk e-mailing
Programming
Single-threaded progress indicator in c#
Reference
Database menu items
Import XML
Save Copy As
Integrity Check
Change Password
Database Properties window
Opening the database properties window
Record types tab
Display types tab
Roles and Users tabs
Sidebar tab
Database ID/Links tab
Counters tab
Building blocks
Building 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 topics
Expression 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
| Programming homeWe're all in favor of lowering our workload, right? There are a lot of ways to leverage what's already built into Axisbase while also writing your own code. The supported language is c#.NET. The basic ways to use and extend Axisbase are:
Click the links above for details on each method. Axisbase primitive typesThe Axisbase types are defined in AxPrimitive and closely map to c# types. The Axisbase type AxPrimitive.INT32 maps to System.Int32 as expected and the other numeric types, DateTime, and bool also map as expected. In addition:
Suggestions for programmingSetup tasks: Many applications have an administrative interface used by one or a few people, distinct from the public interface used by many people. Consider using the Axisbase client for all the setup tasks, such as entering in lookup lists. This costs you zero programming time. Then your public application can be scaled back to just the business-critical processes; it doesn't need to include the setup and administrative interfaces at all. Grids: The Axisbase list viewer is intentionally scaled back for ease of use. It only offers basic sorting and filtering. But you can buy .NET grid controls for power users that offer complex grouping and filtering, re-ordering columns, and formatting features. You might consider writing custom forms that use a power-user grid, with Axisbase data. That form can be in your own standalone application, or as a form inside Axisbase. Some recommended grid controls are:
Security: When considering security in your application, it's best to put it as close to the data as possible, instead of in the user interfaces. Think of the data store as king, and the security rules and business logic code as the royal guards. No matter what client process is used to read and write data, it must get by the guards to reach the king. Therefore, you don't have to write security code in the client program at all (or it can exist in an advisory role). Each user's workstation can have the Axisbase client, and you could allow all users to connect directly to the database, as long as you ensure that their user names are associated with roles having the appropriate permissions. |