Promotic
WikipediaLinkedInYoutubeTwitterFacebook

Access backup data saving (Database Access backups) (obsolete)

Description:
The window serves for setting the parameters for the data storage into the Microsoft 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 count is defined. If one table (backup) in the database is filled up (the size of data in the table exceeds the defined value), 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 script method.

Caution: Two different PmTrend objects cannot be set so that they store the data into one *.mdb file.

The variable name in Data page 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 PmTrend objects used with this storage type in the application, then there can be 63 such objects in one application at the most.
Configuration items:
Data source (ConnectionString)The ADO ConnectionString (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 while the application is launching).

This configurator must not contain an empty string.For example $.join("Provider=Microsoft.Jet.OLEDB.4.0;","Data Source=",$.path("data","trend/"),$.expr("pMe.GroupId"),".mdb;") This configurator must not contain an empty string.
Additional parameters Additional parameters for saving. Allow to define names and data types of system columns, database types based on the trended value 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 with assigned value are separated by a semicolon, 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 while the application is launching).

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 value of the Float64 (Double) data type.This is used if the trended value does not have its database data type defined.(default) "dbdt.f64:DOUBLE;".
dbdt.f32 (optional) - Database data type of the column for trended value of the Float32 (Single) data type.This is used if the trended value does not have its database data type defined.(default) "dbdt.f32:SINGLE;".
dbdt.i32 (optional) - Database data type of the column for trended value of the Int32 (Long) data type.This is used if the trended value does not have its database data type defined.(default) "dbdt.i32:LONG;".
dbdt.i16 (optional) - Database data type of the column for trended value of the Int16 (Integer) data type.This is used if the trended value does not have its database data type defined.(default) "dbdt.i16:SHORT;".
dbdt.u8 (optional) - Database data type of the column for trended value of the Uint8 (Byte) data type.This is used if the trended value does not have its database data type defined.(default) "dbdt.u8:BYTE;".
dbdt.b (optional) - Database data type of the column for trended value of the Bool (Boolean) data type.This is used if the trended value does not have its database data type defined.(default) "dbdt.b:BIT;".
Backup (table) name prefixFirst part of the backup name (table inside the *.mdb file). The complete backup name consists of this prefixem and the serial number.

The backup names creation can be modified using the onBackupCreate event i.e. using self defined backup names.

Macro expression can be used for input (it is evaluated while the application is launching).

This configurator must not contain an empty string.
Backup size by records countThe size of one backup (or table) is set by the records count. If the current size of the table exceeds the defined size of one table on writing new record, new empty table is created into which new and also every other record is written. The value -1 means that the size of backup is not limited by the records count.
Backup size by time intervalThe size of one backup (or table) is set by the time interval. If the time size of the data in the table exceeds the defined time interval of one table on writing new record, new empty table is created into which new and also every other record is written. The value unlimited means that the backup size is not limited by the time size.
Backups countBy continual writing, new tables (backups) are created. Their maximum count is defined by this configurator. If there is defined, for example, the maximum count of backups to 10 and 11th backup is created, the backup with the oldest data is removed and the backups count is still only 10. The value -1 means that the backups count is not limited.
© MICROSYS, spol. s r. o.Tavičská 845/21 703 00 Ostrava-Vítkovice