• Clients
• FAQs
• Programs
• Tips
• Fees
|
|
|
AIMS Backups
View or download the Help File for AIMS_Backups
Purchase AIMS BkUps.aex
Download Latest Update (registered users only)
ABOUT THE AIMS BACKUPS: See a screenshot Run a Backup Demo Run a Restore Demo
AIMS Backups is an addin created by AIMS DataCom for Alpha Five version 5 and later to make it easier for the user to backup data files or application files separately. The two new functions provided, BkUp_Data_Zip() and BkUp_App_Zip(), will always store all Data files or all Application files depending on which one the user selected. They also add the ability to backup other files that are not part of the standard Alpha Five backup routine.
All selected files (application or data) will be compressed in Zip format and stored in a sub-folder of any drive that can be written to directly. Once saved, the files can be restored either all at once or by selecting specific files.
The addin also makes it much faster for the developer to add these features to an application because the functions are already designed to work with any database.
A regular windows help file (download above) is included to help the user and the developer with all aspects of using the backup routines.
INSTALLING THE AIMS BACKUPS:
To install the backups, simply run the installation routine which installs the AIMS_BkUps.aex file to your Addins_Installed folder and create a button to allow the user to start the backup.
Here is a sample script that would allow the user to select either backup routine:
(this script can also be found in the Help file)
resp = ui_get_list( "SELECT BACKUP TYPE", 1, "Data Backup", "Application Backup" )
SELECT
CASE resp = "Data Backup"
bkup_data_zip()
CASE resp = "Application Backup"
bkup_app_zip()
END SELECT
If you only want the user to run data backups, just create a button with only the bkup_data_zip() command.
If you would rather have the backup routine available to only one or selected applications, simply move the AIMS_BkUps.aex file to the application folder. When an aex file is in the application folder, it will only be available to that one application. When an aex file is in the Addins_Installed folder (which is under the A5v5 program folder), it is available to all applications.
DATA BACKUPS:
The data backup function will backup ALL data files (.dbf, .fpt, and .cdx) from the application directory. Even tables which are not listed within the application itself will be backed up. This was done because some applications use external tables for lookups and other purposes. While this may result in backing up unnecessay files in a development environment, it usually works quite well for finished applications.
The developer can include additional data files in the backup by listing them one name per line (wild cards are permitted) in a text file called "addl_data_bkup.txt".
Other available options are:
- The choice of backing up the index files or ignoring them. The default is to back them up and this is generally the recommended method.
- Selection of a different backup folder.
- Deleting all previous data backups in the current backup folder. This option should only be used if you are using a backup method that recycles previous daily/weekly backups. Open the Help file for more details.
APPLICATION BACKUPS:
Although most users will have no need for a backup of the application files, there are at least three advantages to having this capability.
- Some users just feel better just knowing they have the ability.
- It can be very handy for developers who want to make a change but also want to have a backup readily available just in case something goes wrong.
- Some applications may get modified by the user and this provides a simple way to get an up-to-date copy.
The application backup function will backup all application files (data dictionary files -- .dd*, .se*, and .al* ) from the application directory. Even files for tables, sets, or application libraries which are not listed within the application itself will be backed up. This was done because some applications use attached libraries to provide additional scripts/functions and 'external' tables/sets for lookups and other purposes. While this may result in backing up unnecessay files in a development environment, it usually works quite well for finished applications.
Also, all files in the application folder with the '.aex' extension (compiled Alpha Five addin files) and all .bmp, .jpg, .hlp, .chp, .txt, .asc, .csv and .amq files will be included in the backup. (The .amq file is included because of a special text file used by the AIMS Network Optimize routine Opt_net_v5.)
The developer can include additional files in the backup by listing them one name per line (wild cards are permitted) in a text file called "addl_app_bkup.txt".
Other available options are:
- The choice of compacting the data dictionary files before storing them. The default is "No" since they should not normally be changed by the user.
- Selection of a different backup folder.
- Deleting all previous application backups in the current backup folder. This option should only be used if you are using a backup method that recycles previous daily/weekly backups. Open the Help file for more details.
MORE INFORMATION:
For more information, download or view (open) the AIMS Backups Help File.
|
|
