Neblog

One of the most common inquiries we see in MV forums involves exchanging data between the MV DBMS and relational databases. In this multi-part series over the next couple weeks, I’ll describe ways to get data flowing in both directions without using platform-specific ODBC tools.

This Part 1 is just an introduction and I’ll start describing some details in Part 2. I expect a new segment on this every 4 days or so, maybe with other blog postings in between.

(more…)

Almost two years ago I wrote a blog entry titled "Why mv.NET?" But every couple of days we still see the same question phrased differently: "How do I connect to/from MV?" My immediate response is still to include mv.NET in your list of options. Here is an explanation why.

(more…)

I just finished setting up the latest mv.NET v3.5.1.2 and used the Data Manager to create simultaneous connections to multiple MV environments. I dunno if other people get as much of a kick out of this as I do but just the ability to do this tickles me.

(more…)

OK, the title is a little tacky, but if you’re humming a tune about San Jose California then you get the joke. In response to a posting to the U2 User’s list I decided to post some comments here about Service Oriented Architecture.

(more…)

The following is some great information posted to the Raining Data web forum by Robert Burke, their new Technical Support Director. I’ve posted it here verbatim for your benefit.

(more…)

I have code that updates the Outlook Calendar from MV apps. I decided to hook it up with DesignBais. This is just too cool.

(more…)

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. Wow, that’s neat and it all works - but is this good coding practice?

(more…)

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.

(more…)

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 article focuses on some of the advantages of mv.NET over competing products.

(more…)