Alpha Five File Types
If you look at an Alpha Five database through Windows Explorer, you will see that there are many files that begin with each table's or set's name, but have different file extensions. The following table provides a cross reference to lists of functions and methods relevant to each file type.
|
Context |
File Extension |
Description |
References |
|
Database (Library) |
.ADB |
Contains the filenames of all tables and sets that are members of the database and the names of all libraries that have been attached to the database. |
|
|
.ALB |
The data dictionary for an .ADB file. Contains settings, pointers to all scripts, user defined functions, menus, toolbars, bitmaps, and import definitions that have been defined for the database. |
Storing Scripts in a Library, Attaching a Library to the Current Database | |
|
.ASI |
This file stores web application variables. |
||
|
.ALM |
Stores all scripts, user defined functions, menus, toolbars, bitmaps, and import definitions used by more than one table. |
||
|
.ALX |
Alpha Five uses the .ALX file to find a specific script, function, operation, setting, etc. that is stored in the data dictionary. |
||
|
.ASX |
A temporary file containing the indexing information generated by a query against a set. These files may be deleted. |
| |
|
.ADBLOCK |
A temporary file used to prevent more than one user from refreshing a shadow database at one time. |
||
|
Table |
.DBF |
Contains the table's data, one or more records, each containing one or more fields, and the definition of the table's structure. System toolbars are stored in a_toolbars_customized.DBF and system menus are stored in a_menus_system.DBF. |
Table Functions and Methods, Record Functions, Field Functions and Methods |
|
.CDX |
Contains the table index(es). This file is only present if you define index field(s). Alpha Five uses indexes to quickly find records. |
||
|
.FPT |
Contains memo fields, which are text fields of arbitrary length. This file is only present if you define memo field(s). |
| |
|
Data Dictionary |
.DDD |
The table's data dictionary, which contains lists of additional table objects such as Layouts (forms, browses, etc.), report designs, saved operations, field rules, and field names longer than 10 characters. |
Dictionary Methods, Reading From and Writing To the Data Dictionary |
|
.DDM |
Stores additional table objects such as Layouts (forms, browses, etc.), report designs, and saved operations in memo format. |
||
|
.DDX |
Contains the dictionary's index(es). Alpha Five uses the .ddx to find a specific form name or field rule or whatever is needed. |
||
|
Set |
.SET |
The set's data dictionary, which contains lists of additional set objects such as Layouts (forms, browses, etc.), report designs, saved and operations. |
|
|
.SEM |
Stores additional set objects such as Layouts (forms, browses, etc.), report designs, and saved operations in memo format. |
||
|
.SEX |
Contains the set's index(es), used to find set components. |
||
|
Web Publishing |
.A5W |
An Alpha Five HTML page that may also contain Xbasic and Javascript code and web components. The Application Server interprets the Xbasic and web components into HTML or Javascript and delivers the resulting page to a web browser. |
|
|
.A5WCMP |
A file that contains the definition of an Alpha Five web component. A5W pages may contain one or more web components. |
||
|
.WCP_Settings |
Stores Web Project settings specific to a profile. |
| |
|
.WebPublishHistory |
Stores publishing history information and is used to determine what needs to be published. |
| |
|
Other |
.MPX |
A temporary file containing the indexing information generated by a query against a table. These files may be deleted. Alpha Five should delete them when exiting. |
|
|
$$... |
|||
|
.AEX |
Compiled library script files. |
||
|
.CHM |
Compiled Windows help files. |
||
|
.HLP |
Standard Windows help files. |
||
|
.LOG |
Error and transaction logging files. |
||
|
.BML |
Image library files. |
||
|
.EXE |
Alpha Five program files. |
||
|
.MUF |
Alpha Five creates temporary .MUF files to control the number of people who can concurrently open a database. If a user has a 3 user a5 license, then: when person 1 opens the database, the .MUF file with the same name as the .ADB file is created and a count of 1 is recorded in the .MUF file. When person 2 opens, the count in the .MUF file is increased to 2. When person 3 opens, the count in the .MUF file is increased to 3. When person 4 tries to open the count in the .MUF file would exceed the number of licenses, so person 4 gets an error message. When person 3 closes, the count in the .MUF file is reduced to 2 and person 4 could open. When all users close the count in the MUF file is 0 and the .MUF file is deleted by Alpha Five. If a crash occurs the .MUF file may be left on disk, preventing other users from accessing the application. In this case all users should exit Alpha Five and the MUF should be manually deleted. |
||
|
.RMUF |
The Alpha Five Runtime keeps track of the number of simultaneous users using a file with a .RMUF extension, which has the same functionality as a .MUF file. |
See Also
Supported By
Alpha Five Version 5 and Above