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
| Connecting to a sample databaseThere is a sample database hosted on axisbase.com, which you can connect to. For general information on connecting to database, see Using the launchpad and opening databases. To connect, press Connect to Server in the Axisbase launchpad.
Enter these values:
The sample database has customers and sales in it, using auto-generated names built from random dictionary words. The guest user has rights to edit customers and sales, but not change record types or building blocks. If you want to build onto the sample database for your testing, you can create a database file on your computer and link it to the sample database. Most common connection problemsThe most common connection problems are:
Connection troubleshootingThink of connection troubleshooting like kinks in a garden hose. If you are trying to figure out why no water is coming through, you have to focus on the first kink first. Working with the part of the hose downstream from the kink can never make the water go through. In the same way, network connections involve a series of potential kinks, and only the first one matters at any given point in time. Generally speaking, there are three possible points where a network connection can be blocked:
|