Backup data saving into the Access database (Database Access backups) (obsolete) - configuration window

Description:

The window serves for setting the parameters for the data storage into the Access database. By this technology the data are stored into tables (in the Access database) with the name beginning with the same prefix as the trend group identifier.
The size of one table and its maximum number is defined. If one table (backup) in the database is filled up (the size of data in the table exceeds the defined value), then a new table is created into which it is written from this moment. This walkthrough repeats all over again.
Note: The size of one backup (table) can be set to unlimited and new backups can be created by calling the BackupCreate method.
Caution: Two different PmaTrendGroup objects cannot be set so that they store the data into one *.mdb file.
The variable name on the "Data" tab can be maximum 64 characters long (the length of column name in the Access table is limited). This storage type has a limitation: If there are multiple PmaTrendGroup objects used with this storage type in the application, then there can be 63 such objects in one application at the most.

Configurators:

Data source (ConnectionString)	The ADO ConnectionString (http://www.connectionstrings.com) contains all necessary parameters needed by the ADO Connection object for database connection via the selected ADO Provider. Macro expression can be used for input (it is evaluated after the application is launched). This configurator must not contain an empty string. For example $.join("Provider=Microsoft.ACE.OLEDB.12.0;Data Source=",$.path("data","trend/"),$.expr("pMe.GroupId"),".mdb;") or $.join("Driver={Microsoft Access Driver (*.mdb)};Dbq=",$.path("data","trend/"),$.expr("pMe.GroupId"),";")
Additional parameters	Additional parameters for storing. Allows to define names and data types of system columns, database types based on the trended variable data type. Available parameters are shown in the following example together with their preset values for selectaed saving type (plugin). These values may not be entered. Enter the values only if non-default are needed. Entries are in the KeyVal format, for example "dbdt.pmtime:DATETIME;dbdt.pmattr:LONG;dbdt.f64:DOUBLE;dbdt.f32:SINGLE;dbdt.i32:LONG;dbdt.i16:SHORT;dbdt.u8:BYTE;dbdt.b:BIT;". Macro expression can be used for input (it is evaluated after the application is launched). dbdt.pmtime (optional) - Database data type of the column containing record timestamp. Default "dbdt.pmtime:DATETIME;". dbdt.pmattr (optional) - Database data type of the column containing record attribute. Default "dbdt.pmattr:LONG;". dbdt.f64 (optional) - Database data type of the column for trended variable of the data type: Float64 (Double). This is used if the trended variable does not have its database data type defined. Default "dbdt.f64:DOUBLE;". dbdt.f32 (optional) - Database data type of the column for trended variable of the data type: Float32 (Single). This is used if the trended variable does not have its database data type defined. Default "dbdt.f32:SINGLE;". dbdt.i32 (optional) - Database data type of the column for trended variable of the data type: Int32 (Long). This is used if the trended variable does not have its database data type defined. Default "dbdt.i32:LONG;". dbdt.i16 (optional) - Database data type of the column for trended variable of the data type: Int16 (Integer). This is used if the trended variable does not have its database data type defined. Default "dbdt.i16:SHORT;". dbdt.u8 (optional) - Database data type of the column for trended variable of the data type: Uint8 (Byte). This is used if the trended variable does not have its database data type defined. Default "dbdt.u8:BYTE;". dbdt.b (optional) - Database data type of the column for trended variable of the data type: Bool (Boolean). This is used if the trended variable does not have its database data type defined. Default "dbdt.b:BIT;".
Backup (table) name prefix	First part of the backup name (of the table in the *.mdb file). The complete backup name consists of this prefixem and the serial number. The backup names creation can be changed in the onBackupCreate event, i.e. using self defined backup names. Macro expression can be used for input (it is evaluated after the application is launched). This configurator must not contain an empty string.
Backup creation is defined by records count	If checked, then the backup (creating new file) is performed on achievement of specified record number. If not checked, then the backup size is not limited by record count.
Number of records	The size of one backup (i.e. table) is defined by the record count. If the backup size defined here is exceeded on writing new record, then new empty table is created and the new record is saved here. Following records are saved into this new backup since this moment.
Backup creation is defined by time span	If checked, then the backup (creating new file) is performed periodically with the defined period (every year, month, week, day, hour, minute). If not checked, then the backup size is not limited by time range.
Time span	The backup (i.e. table) size is defined by time span. If the backup time-range in the table defined here is exceeded on writing new record, then new empty table (*.dbf file) is created and the new record is saved here. Following records are saved into this new backup since this moment. 1 year 1 month 1 week 1 day 1 hour 1 minute
The total number of backups is limited	If checked, then the maximum number of the backup count is limited. If this number of files is achieved, then the oldest backup file is replaced by the newest one. If not checked, then the backups count is not limited.
Maximum number of backups	Maximum number of backup files. By continual writing, new tables (backups) are created. Their maximum number is defined by this configurator. If there is defined, for example, the maximum number of backups to 10 and 11th backup is created, then the backup with the oldest data is removed and the backups count is still only 10.