MVpro
Modern tools for your MultiValue application.
Without rewriting it.
MVpro is a 4GL development and runtime environment for MultiValue applications. It separates your application from your database, moving the data layer to SQL Server, Oracle, DB2, or U2, while your application continues running in MultiValue BASIC. Your team gains modern IDE tooling. Your business preserves its software investment.
The challenge
Your application still drives the business. The environment around it is the constraint.
The logic embedded in your MultiValue system reflects years of development and deep domain expertise. It is proven, stable, and central to how your organisation operates. Replacing it from scratch would introduce unnecessary cost and risk.
The problem lies in the environment it depends on. Development tooling has remained largely unchanged for decades. The database is tightly coupled to the application, making infrastructure changes complex and high risk. Recruiting MultiValue BASIC developers is increasingly difficult, and the number of people who understand your specific implementation continues to shrink.
MVpro modernises the environment without replacing the application. Your business logic remains intact. Your database moves to SQL Server or Oracle. Your developers work in Visual Studio Code with modern debugging capabilities. Deployment timelines shift from years to months.
MVpro and MVsharp: which one?
Choose MVsharp when:
You want to convert your MultiValue BASIC code to C# .NET source code and migrate your data to SQL. Full conversion to a .NET and SQL environment, with the resulting codebase maintained by standard .NET developers.
Learn about MVsharp →Choose MVpro when:
You want to keep your application running in MultiValue BASIC while modernising the database layer and development environment. The application language stays. The database, tooling, and deployment model modernise.
Key capabilities
A modern environment for your existing application.
Application and database separation
MVpro decouples your application layer from the database layer. Your MultiValue application logic runs unchanged while the database moves to SQL Server, Oracle, DB2, or U2.
Modern database support
Deploy your MultiValue applications against SQL Server, Oracle, DB2, or U2 (UniVerse and UniData®). Move to the database your infrastructure team already manages.
Visual Studio Code integration
Develop in Visual Studio Code with purpose-built MVpro extensions for MultiValue BASIC, C#, visual debugging, and TCL. Your team uses modern tooling without abandoning the language they know.
MVpro Developer Studio
A dedicated GUI development environment for MultiValue BASIC. Build, test, and deploy from a single studio without switching between tools.
Rapid prototyping and deployment
Build and test new application features without a system rewrite. MVpro supports rapid prototyping from existing MultiValue codebases, cutting deployment timelines from years to months.
Code analysis
Identify unused and defective code across your existing MultiValue application. Understand what you have before deciding what to do with it.
How it works
Modernise the environment. Keep the application.
Assess
MVpro code analysis tools identify unused and defective code across your existing MultiValue application. You understand what you have before making any changes.
Separate
MVpro inserts a runtime layer between your MultiValue application and its database. The application continues running. The database connection is now managed by MVpro.
Migrate
The database moves to SQL Server, Oracle, DB2, or U2. Your application code does not change. The new database is managed by your existing infrastructure team.
Develop
Your development team switches to Visual Studio Code with MVpro extensions. Debugging, code analysis, and development now happen in a modern IDE with modern tooling.
Where it fits
The application layer in the Prosol platform.
MVpro sits alongside MVsharp at the foundation of the Prosol platform. Where MVsharp converts MultiValue code to .NET, MVpro modernises the environment around the existing MultiValue code. The two are often used together, with MVsharp handling the database conversion and MVpro handling the application layer and development experience. Both open the path to MVsync, MVrest, and i-Con above them.
See the complete platform →In practice
MVpro in the field.
Vehicle finance system on Azure
A leading African bank used MVpro alongside MVsharp to migrate its vehicle finance system from a legacy MultiValue platform to Azure. The system now runs on modern cloud infrastructure without losing the application logic built over decades.
Bringing a MultiValue product to modern platforms
Independent software vendors with mature MultiValue products use MVpro to port their application to modern databases and deployment environments, opening new markets without the cost and risk of a full rewrite.
Developer team modernisation
Organisations where MultiValue expertise is ageing and hard to replace use MVpro to transition development to Visual Studio Code and modern tooling, making the codebase accessible to a wider pool of developers.
Technical specifications
Supported environments
- Supported databases
- SQL Server, Oracle, DB2, U2 (UniVerse and UniData®)
- Primary IDE
- Visual Studio Code with MVpro extensions
- Extensions
- MultiValue BASIC, C#, Visual Debugging, TCL
- Additional IDE
- MVpro Developer Studio (GUI)
- Import from
- Popular 4GL environments
- Application interfaces
- Character, graphical, and browser-based
Often used with
Related products
MVsharp
MVpro and MVsharp are frequently deployed together. MVsharp converts the database and code to .NET; MVpro handles the application layer and development environment.
MVsync
Once MVpro has moved your database to SQL Server, MVsync keeps data synchronised with any remaining MultiValue systems during a phased migration.
i-Con
Use i-Con to connect the modernised MVpro environment to the rest of your application landscape.
Modernise the environment your application runs in.
Talk to a Prosol specialist about your MultiValue application. We will show you what MVpro changes, what stays the same, and what your development team gains from day one.