•Now users can manually add data, using Storage.CreateNewSession, to a Storage object without configured fields. This bug occurs since v2.5.102.

•The compression algorithm of the Storage now discards consecutive data which have the same timestamp, using only the last value of a sequence of values with the same timestamp. This bug occurs since v1.20.354.

•Corrected the behavior of MinRecTime in the compression algorithm of the Storage, which in certain situations was recording data without respecting the time configured in MinRecTime. This bug occurs since v1.20.192.

•Corrected a problem in the compression algorithm of the Storage which made the linking record of MaxRecTime not being recorded in some situations, or recording two records when reaching MaxRecTime instead of one. This bug occurs since v2.5.102.

•Corrected a problem in the SampledData Query of the Storage which failed if at least one of the Query Tags had duplicated data, more than one value at the same timestamp, at the beginning of the Query period, or at the end of the period. This bug occurs since v3.0.150.

•Corrected a problem in the compression algorithm of the Storage, which made the linking record of MaxRecTime being generated with an incorrect timestamp in certain situations, may leading to incorrect data interpolations. This bug occurs since v2.5.102.

•Corrected a problem in the Storage, which lead to a failure when creating tables with more than 100 fields in Access databases. This bug occurs since v1.21.43.

•Corrected a problem which deleted Storage fields in the database if there were duplicated fields in the Storage configuration. This bug occurs since v1.21.43.

•Performed several improvements in the Storage to avoid creating duplicated fields in the database, or preventing duplicated data to be recorded in a Storage field. Logs generated by the Storage were improved to provide a more accurate diagnosis of configuration errors and problems found at run time. This bug occurs since v1.21.43.

•Corrected a problem when updating Stored Procedures used by the Storage in SQL Server, which were always deleted and recreated as soon as the Database Server was activated, which could lead to problems on queries from other Database Servers using the same database. This bug occurs since v1.21.26.

•Fixed a problem occurring when Storage was executed with more fields than the available licenses, which lead the first field of each table to be erased, and the last field to be duplicated. This bug occurs since v3.5.285.