Providing Apps in a MultiValue Environment

As we slowly recover from the Covid-19 pandemic the affects and implications of the pandemic are still very much evident. What is also very evident is the determination of business to not only address the current conditions but to plan for the longer-term effects of the different working practices and customer buying options. As a result, an ever-increasing number of companies are looking at the introduction of new mobile and desktop apps as a way of connecting directly with their customers, partners and staff.

Companies that use MultiValue technologies are no different, they have the same business requirements as everyone else. But as we have seen so often, many MV based companies have been conditioned to accept they are not able to take advantage of modern technology because of the significant custom developments that form part of the majority of MultiValue environments and the multi-valued data structures.

It is often said that the MultiValue database is different and to alter the structure of the existing database to work with new technology is not something they even want to think about. Similarly, the investment in years of adding and refining DataBasic logic and routines is seen as too great a commitment to consider redeveloping the applications.

But now more and more MV based companies are discovering Evoke, a no-code/low-code app development platform that works seamlessly with all aspects of MultiValue just as well as it does with SQL. As a result, MV users have been able to introduce new apps based on new technology, without having to change any part of their existing systems.

So, what is different?

First, with Evoke you do not have to change your database, the structure of your database or any part of your database. It works with all types of databases (SQL, all flavors of MultiValue, Oracle, DB2). There is full support for the use of an existing data structure (embedded multi-values, embedded sub-values, remote keys, local keys, etc.).  You can also include multiple databases and multiple types of databases in a single app design. For example if required, an Evoke app can use an SQL Server database to manage a Products table, a UniVerse database to hold and manage Orders, a D3 database for Suppliers and a jBASE database for Users/Personnel, etc. All will work seamlessly together and interact within the same Evoke designed app.

Evoke will automatically generate the MultiValue CRUD (Create, Read, Update, Delete) code (in the appropriate flavor of DataBasic) as the complete integration layer between the app and the MV database. It also lets you define the data model you require for your app and map that on to your database layout and structure. This allows you to design your apps to fully meet your company’s business requirements, independently of your current database structures and restrictions. Evoke will even automate the creation of the Evoke data model based on your existing MultiValue database schema layouts.

In addition, Evoke provides MultiValue users with the ability to incorporate their existing DataBasic (Proc, Python, etc.) code, new code and even 3rd party software in to the their apps. This means that there is absolutely no wasted investment, duplication of work nor the feared, ‘rip it up and start again’ scenario.

When combined with an unrivalled level of support not normally seen in the MultiValue world provided at no additional cost directly from BlueFinity, our customers see an easy, cost effective and unencumbered route to implementing modern app technology as an integrated part of their existing MultiValue framework. This means that all companies can now introduce apps created by existing staff that uses drag & drop, point & click and option select methodologies that eliminates perceived MultiValue limitations!