Two types of reusable web components can be created by any developer with a good knowledge of Xbasic, HTML, and JavaScript. One type is the Custom Component, discussed in this article and those following. The other is the User-defined Component, which is both more flexible and harder to develop. We recommend starting by creating a Custom Component even if your ultimate goal is to develop a User-defined Component.

A User-defined Component is the more flexible big brother of a Custom Component. Like a Custom Component, a User-defined Component can be opened in a window, a DIV, or a Tabbed UI Pane, in a linked content section of a Grid, and in a row expander of a Grid. Like a Custom Component, a User-defined Component has bindable arguments.

Topics covering Javascript in UX Components, where it can be added, and using various Action Javascript actions that are available.

The Grid Component now fully supports the use of 'sequences'. Some databases, such as Oracle, implement auto-increment fields through the use of 'sequences'. A 'sequence' is an object that is used to get the next number for an auto-increment field when a record is inserted. In order to use a sequence to generate the ID values for an auto-increment field, you need to tell the Grid component what the name is of the sequence to use.

Pages relating to Javascript used in the Grid Builder.

Components are collections of client-side and server-side code that give your application its look, feel, and functionality. You create them through the use of component builders in the Alpha Anywhere Developer IDE. There are currently 15 types of components, each with a corresponding builder. Most of these are for specific tasks such as the Video Player component for playing videos, and the Google Map component for displaying maps. There is also a special component called the UX component, which is used to build the application's interface. In practice, many mobile applications will consist of just a single UX component.

After you have defined all security parameters, you may build a login component. A login component may include up to 3 "views". All login components have a login view. This includes the fields for entering a user ID and password and may include links to other views. If the security settings allow a user to change his or her password on-line, a second view named "Change Password" is available. This allows you to configure a specific component layout for changing passwords. If the security settings allow the user to recover lost login information, a third view named "Lost Info" is available. This will show various fields that are used to verify the identity of a user and return the requested login information.

The Web Projects Control Panel has several tools to assist in the management of the files that are used to compose web pages.

To use the ADO Import Genie, you must have ADO available. To have ADO available means you must have MDAC installed. If you have problems with MDAC, this link takes you to a Microsoft utility named Component Checker that can repair you MDAC installation. From the Microsoft site: "Component Checker utility has been redesigned to provide XML support. The new tool includes updated snapshots for MDAC 2.7 SP1 on Windows XP SP1 and MDAC 2.8 SP2 on Windows Server 2003 SP1. The Component Checker tool is designed to help you determine installed version information and diagnose installation issues with the Microsoft Data Access Components (MDAC)."