Support >> FAQ

Platform Availability

A fundamental design aim for mv.NET was to provide connectivity to ALL the main MultiValue databases. We have done this and are providing the developer with the greatest flexibility to deliver applications across the widest range of databases.  We also know that many organizations like the comfort zone and don’t want to have to install the “latest” database release, so mv.NET is not ageist and will run on many of the old releases.  Today we support D3, jBASE, mvBASE, QM, Reality, Power95, UniData, UniVerse and UniVision and have immediate plans for mvEnterprise and possibly Revelation.

Database Access Licensing Requirement 
An mv.NET Database Access License is required for each concurrent database connection established by one or more mv.NET clients (be that a rich client or web-based service thread).  The number of licenses required will depend on the application design and implementation.  It should also be noted that each mv.NET database connection/session will, when active, consume a MultiValue database license.  mv.NET Server can be installed on Windows and Unix MultiValue databases, whereas an Operating System compatible with Microsoft .NET Framework is required to deploy the application.   

Developer Requirement
Each Developer Workstation will require an mv.NET Developer License on their PC or Workstation.  Windows Operating System compatible with Microsoft .NET Framework and Visual Studio .NET 2003 is required.  Each license is supplied with two database sessions/connections which will, when active, consume a MultiValue database license.  mv.NET Server can be installed on Windows and Unix MultiValue databases