Release Notes: Zim 8.50 for Windows (build 4232) - April 2017


Improvements and Fixes

Preserving Data When Changing Entity Set Definitions

The process of saving and restoring database data has been redesigned to ensure more reliability,

particularly when recreating entitysets and data relationships. A new table called ObjectSaving

was introduced to keep track of the all database data saving and loading. It contains the name and directory

of the saved object along with the data save document name, filename and directory, number of records

loaded and restored, dates and times.

When you ZOMDataSave an object, all information is written to the table ObjectSaving and when you try to load

the data using ZOMDataLoad, all the information needed is retrieved from the table.

This process implies that, in order to load data using ZOMDataLoad, you must have executed a ZOMDataSave

previously to populate the Objectsaving table with the proper information.

Therefore, if you need to load data into a table that had never been unloaded before, run a ZOMDataSave on this table,

even if the table is empty, to include the needed information in the ObjectSaving table.

If the data save document name is not specified on the ZOMDataSave command (option “;d <docname>”) ,

the name will be formed by the first 13 characters of the table name followed by a five digits number

generated from the table name and its directory.

Similarly, if the filename is not specified (option “;f <filename>”), it will be formed by the table full name

followed by the same number used in the name of the document.

The ObjectSaving table stores a trace of data loads and unloads of each object in the database.

All data save files are stored in the directory zomsaving in the database directory.

ZimExplore Secure Log In

ZimExplore allows the administrator to control the overall work performed by ZimServer. As such,

the administrator needs privileges to perform critical actions. This is provided by a specific user name and

password for each server machine. After a normal login, by rightclicking and selecting "Edit" on the desired server,

a new user name and password can be chosen. For this moment on, these are going to be the new credentials to

access that specific server via ZimExplore.

 

Warning: after changing the credentials and if they are "forgotten", the only way to make ZimExplore to work again

is to fully re-install the Zim 8.50 product.

The "Save As..." Functionality

The $FileBrowse function only allowed the user to select an existing file from the file system.

Now, this function was extended to select a file for saving, thus implementing the "Save As..."

functionality. Usually, this file name will not exist, but, if existing, a message will be raised.

To perform this action, the Zim programmer needs to set the Flags to "0" (zero) with the other

parameters working as documented, including the return of the function which indicates the full

path of the file selected for creation. This file name then should be used to copy (using the

function $CopyToClient, for instance), the desired file over the "save as..." destination.

 

Release Notes: Zim 8.50 for Windows (build 3951) - May 2016


Improvements and Fixes

1) Increased stability for ZimIDE

2) Improved ZimIDE error handling and error message reporting

3) ZimIDE and ZOM (Zim Object Manager) communication

4) General bug fixes and improvements to all components

5) Default value for entity sets were not being saved correctly

6) Relationship conditions are now validated

7) Relationship builder for Relationship management

 

Recommended Database Checks and Updates

To ensure your databases have the latest ZOM version, always run an update before working with your database. This is highly recommended when you install a new Zim 8.50 build, and mandatory everytime you create a new database:

 

1) Connect to the database using ZimQt Client.

2) At the prompt, run:

>ZOMEnable to update ZOM and the Data Dictionary to the current version.

 

Known Issues

1) Barcode, Listview, Gridview Widget have not been fully implemented in ZimIDE

2) Relationship Condition Checker may not detect all error conditions

3) "ENDTRANSACTION was invoked without a previous TRANSACTION." Warning message may appear in the workpath's "errors.trc" file when modifing Entitysets

4) ZimServer must be run as an application. ZimServer as a service is not working in this release

5) ZimIDE is not preserving data in Entitysets or Relationships with fields when these object types are changed or modified. To prevent loss of data, use the ZOMDataSave before the change and ZOMDataLoad after

 

Melhorias e correções

1) Aumento da estabilidade do Zim IDE

2) Melhoria no tratamento de erros e sua descrição

3) Melhor comunicação entre o Zim IDE e o ZOM (Zim Object Manager)

4) Correçãos de bugs em geral e melhorias em todos os componentes

5) Valores default de entidades que não eram salvos corrigido

6) Condições de relacionamento inválidas agora são validadas diretamente

7) Introduzido um construtor de condições de relacionamento dentro do IDE

 

Recomendações e atualizações recomendadas para o seu banco de dados

Para garantir que seu banco de dados têm a mais recente versão do ZOM, sempre executar uma atualização do BD antes de iniciar a trabalhar com ele. Isto é altamente recomendado quando você instala um novo build do Zim 8.50 e obrigatório quando você cria um novo banco de dados. Para tanto siga os seguintes passos:

 

1) Conecte-se ao seu banco de dados usando o ZimQt Client.

2) No prompt do Zim executar:

>ZOMEnable Para fazer o update do dicionário de dados e atualizar o ZOM.

 

Problemas conhecidos

1) Os objetos gráficos Barcode, Listview, Gridview Widget nao estão ainda completetamente implementadas no presente build do Zim 8.50

2) O verificador de condições de relacionamento pode não detectar todas as condições de erro possíveis

3) Uma mensagem de "Warning: ENDTRANSACTION was invoked without a previous TRANSACTION." pode ser exisbida no arquivo "errors.trc" durante a criação/recriação de uma entidade ou relacionamento com campos. Esta mensagem pode ser ignorada

4) O Servidor Zim deve ser executado como um aplicativo. O servidor como um serviço não está ainda totalmente implementado neste release

5) O Zim IDE não está salvando os dados existentes em entidades ou relacionamentos com campos quando estes objetos são alterados. Para evitar a perda de dados utilize o ZOMDataSave antes da alteração e o ZOMDataLoad após