Caliach Vision V5.00 operates with Omnis Studio V6.10 or greater.
The following relates to changes made since V4.1000.
Caliach Vision V5.00 has been rewritten from V4.10 to use an external SQL Database Server engine. In previous versions the program used the Omnis Native Datafile system. Although this was remarkably successful and reliable it is essentially 1980's technology that since the early 1990s has not been enhanced, has limits of scale and is not transaction-safe. Modern server-based data engines offer much greater scalability, greatly improved performance and are extremely robust even under heavy multi-user loads. The program functionality has remained substantially the same as V4.10 with some additions to accommodate SQL management and some utility functionality has been deprecated. For an introduction see Client-Server SQL Introduction
What has changed as a consequence can be summarised as follows:
File -- Preferences -- Database Logon Settings
File -- Preferences -- SQL Log Review
Allows you to examine the raw SQL sent to the server typically by Dynamic Queries. Opens the SQL and Error Log Review window.
File -- Advanced -- SQL Statements Manager
Maintenance of Dynamic Queries, Sort Sets, Where Shortcuts, Join Shortcuts and Statement Shortcuts all stored in the Extras\Statements.db database. Opens the SQL Statement Manager window.
File -- Advanced -- Create New Database and Copy Data
Allows you to create a new database and copy the main database data, including on a different SQL DBMS. For instance, you can clone you current PostgreSQL data to a SQLite database to carry on a laptop with no need of additional software. Opens the Create New Database and Copy Data window.
File -- Ad Hoc Reports
Ad Hoc Reports are no longer needed. Other third-party products are widly available and much superior.
File -- Ad Hoc Graphs (Old Type)
This used an external that Omnis no longer supports. Use Graphs 2 instead.
File -- Advanced -- ODBC File Access
ODBC access to data now requires propitiatory software generally available free on the Internet.
File -- Advanced -- Data File Browser
Only applicable to Omnis Native Datafiles.
File -- Advanced -- Re-Size Data File
Generally there is no need for this with SQL databases.
File -- Advanced -- Create New Data File
Now replaced by Create New Database and Copy Data (see above).
File -- Advanced --Data Fix Utility
No need of this with modern database engines.
File -- Advanced -- Special Functions Utility -- Export Data to Palm III Organiser
File -- Advanced -- Special Functions Utility -- Set Files Read/Write
Not relevant with SQL databases.
With the move to SQL (Structured Query Language) there is a need to change the terminology used in the past with Omnis Datafiles:
Database has replaced the word Datafile. SQLite uses a single operating system file for a single database whereas server database engines can have many databases within them. Caliach Vision connects to one named databse at a time (except for the Copy Database function).
Table has replaced the word File that was used to describe a data set in OND. Tables can be thought of as spreadsheet pages with a defined number of columns and 1 or many rows. There are many tables in a database. A table is defined as having a number of columns, each of a particular data type. For example the parts master table (PTMFILE) has a part number column and a description column. Each entry in the parts master is a row of data with the same columns.
Column has replaced the word Field that now can revert to it's generally understood meaning of the box you type data into on a window. The field on the window often maps onto a table column in the data.
Row has replaced the word Record that was used to describe an entry in a table.
Schema classes and Table classes have replaced File classes inside Caliach Vision. There is one Schema for each Table (or old File) of data. On client-server data systems the server must hold the data structure but Caliach Vision needs this too. Schemas provide for that and mechanisms are automatically applied to synchronise the server engine if changes occur in the Schemas, rebuilding data if needs be. While Schemas are just data definition repositories, Table classes are mapped dynamic objects that contain functional programming code for data retrieval and manipulation. The two together work hand in glove to connect to the server engine through DAMs (Data Access Managers) which can be thought of as software drivers for communication and translation for a specific engine, SQLite, PostgreSQL and MySQL (MariaDB is a shoe-in for MySQL).
Caliach have maintained the V4.10-style installation that integrates Omnis Studio into the Caliach Vision folder structure so that just one location on your computer contains all files related to Caliach Vision operation. For Microsoft Windows Vista, Server 2008, 7, 8 and 8.1 this breaks the convention of placing executable files in the Program Files folder of the C drive and the subsequent security enforcement of UAC. However, it is our view that this breach is well worth it for the convenience and of a simple, compact, self-contained and integrated structure.
There are in all 4 installers. A full and demonstration version of each of our supported platforms, Windows and MacOSX. The Demonstration edition contains pre-licensed Caliach Vision and Omnis Studio Runtime and operates on a SQLite engine. The Full edition contains a full set of Caliach Vision files and both Omnis Studio Runtime and Design programs with user control to include the Design program, typically only needed by the system manager. All versions include our 10 additional program languages. However, unlike V4.10 there is now only one TrainingDemo database which when used on the demonstration license self-translates the data to your selected language dynamically.
The installer by default names the folder containing the installation with the version number, so the full version will go to C:\CaliachVision-5.00. If that already exists files within it will always be overwritten. Extra files you have created such as Archive files will still remain but if you have archive or custom files from an older version, it is left to you to copy them to the new folder structure from the old one.
Menus items that have been added are:
Window Tab Panes that have been added are:
Fields you may want to populate
The following options have been added. For a full listing see the Program Options Listing window topic.
If set, the user will receive a warning if they attempt to log on to a Company Name logon that does not conform. This is available to warn users when they inadvertantly choose a backup or play-data set.
The user's last logon company name. This is automatically set in Terminal.inf and used to re-select it as the default at the next logon, when optCompanyNameDefault is not set.
SQL DAMs (Data Access Modules) can create Debug logs to record internal errors. If this option is set to between 1 and 5 a text file named DamDebug.txt will be created in the same folder as Vision.lbs. 1= No debugging but is available, 2= Base level, 3, 4 and 5 are escalating levels of refinement.
Used in conjunction with optUsernameServerN and optPasswordServerN. N=1 for MySQL and 2 for PostgreSQL. Forces the server logon name and password where password entry by the user can be forced.
Only applies for SQLite main database. If set, the Host database file path for SQLite will be prefixed with the contents, when constructing the path. This is useful where users see a server location differently, for instance when mappings are different.
Used in conjunction with optUsernameServerN and optForceLogonEntryServerN. N=1 for MySQL and 2 for PostgreSQL. Forces the server logon name and password where password entry by the user can be forced.
The full path to the folder on the server where common additional files can be found. This acts as the root to the location which may be appended by a Company folder in the Logon Settings. The full path is used to locate supporting files: Extras, Custom, ProgUser.db, ProgSyst.db, etc.
Used in conjunction with optPasswordServerN and optForceLogonEntryServerN. N=1 for MySQL and 2 for PostgreSQL. Forces the server logon name and password where password entry by the user can be forced.
The following options have been and one obsoleted in V5.00 and are no longer used.
This has been obsoleted in V5.00.
optODBDatafile0 to 9 and A to Z
This has been obsoleted in V5.00.
Feature enhancements up to F0513 were released in maintenance updates to V4.0000. F0514 was released in V4.1000.
Please refer to http://www.caliach.com/caliach/support/newfeatures/f40100.xml for details on these enhancements.
Change in the data access and management from Omnis local database (OND) to client-server SQL using SQLite, PostgreSQL, MySQL or MariaDB. All auxiliary datafiles moved to SQLite databases. Addition of Logon.db and Statements.db. Full functionality of V4.1003 retained. Special migration and re-customisation required.
As a result of F0521 feature enhancement the following help pages have been added:
As a result also of F0521 feature enhancement the following help pages have been removed:
No customisation made for pre-V5.00 will function correctly:
The following issues are known to exist and may be resolved in a future release of Omnis Studio:
|Menu Line Functions||777|
|Push Button Functions||2,604|
|Library Bytes Used||31,255,040|
|Library Method Lines||398,967|
|Help Page Files||753|
|Help Graphic Files||1,488|
|Help English Index Words||9,917|
|Translated languages supported||10|
|Translation master english texts||70,269|
|Translation language texts||660,566|
Compiled in Program Version 5.04. Help data last modified 5 Feb 2015 04:35. No class.