Wizard vs Manual Coding of Data Components

mv.NET is a suite of three packages, one of which is the Adapter Objects library. This allows MV data to serve as a data source for ADO.NET just like any relational data source. Using the library can be very easy. In Visual Studio you can drop toolbox objects onto a form. Doing so invokes a Wizard to configure the components. […]

Technology choices: Windows, .NET, and mv.NET

This article discusses why I have chosen to work with Windows, the .NET Framework, and mv.NET for interfaces to MV DBMS applications. Feel free to disagree with my choices but maybe my reasoning will make sense to others who are trying to find their "home" amongst all of the available options.

Why mv.NET?

Connectivity into MV / Pick databases from object-oriented languages and mainstream products used to be difficult. These days it’s not tough at all, and highly affordable as well. There are many tools in our market that can do communications between MV and others, but I’ve settled on one tool that satisfies almost all of my needs for communications development. This […]

How many licenses do I need?

This is an in-depth explanation of how web clients consume licenses with a back-end MV DBMS. It might be too basic for some people but it should help to bring everyone up to a common level for discussions on this important topic.