I'm creating this thread to avoid hijacking the Revelation thread with
more unrelated material.

In response to notes from Jim and Gene: mv.NET now supports MVSP
connectivity to D3 _and_ it supports Reality.

One of many advantages of using mv.NET over native connectivity is
session pooling, which allows you to maximize the efficiency of
existing DBMS licenses.

I wouldn't position mv.NET to replace all connectivity, like MVSP,
QMClient, UniObjects, jRCS, etc. For a good fit, I would recommend
that mv.NET be used for some applications while DBMS-specific tools be
used for others. It's just important to know your options, and I can
help with that.

There are Many more feature/benefits of this excellent software which
is now in use by a significant number of our respected colleagues.

Contact me to discuss your requirements.

Thanks for your time.

Tony Gravagno
Nebula Research and Development
TG@ remove.pleaseNebula-RnD.com
Nebula R&D sells mv.NET and other Pick/MultiValue products
worldwide, and provides related development services
remove.pleaseNebula-RnD.com/blog
Visit PickWiki.com! Contribute!
http://Twitter.com/TonyGravagno

On Jun 2, 4:10*pm, Tony Gravagno <tony_grava... (AT) nospam (DOT) invalid> wrote:

Sorry, but I'm not familiar with MVSP. What is it?

Thanks,

Jim

JJCSR wrote:
MVSP is a new connectivity option for D3v9 and mvBase v3.0. It
essentially replaces the D3 class library for fast remote file access
and code execution, not for ODBC connectivity. There are Java and
..NET bindings, making the connectivity usable from *nix as well as
Windows.

Please check my blog on Monday for a new entry, not a "what is MVSP"
explanation, but a discussion of when to use the Java or .NET
interface, and when to use a product like mv.NET. I had an intro to
MVSP which I didn't publish, and I even wrote a "Using MVSP" mini book
which I haven't had time to edit down. Ahh, so much to write and no
time...

T
remove.pleaseNebula-RnD.com/blog