This same question comes up whenever someone mentions a for-fee component -
"why pay when I can do it for free?" Yes there is a cost associated with
advanced components. We pay other people who make our jobs easier. One
could say there's no reason to use a DBMS at all - why not just store our
data in free tab-delimited files and parse the data ourselves with lots of
custom code? This discussion can go on for a long time and it never leads
anywhere. For those of us in this market who make a living selling
software or services it's especially difficult to maintain the argument
against for-fee components because ultimately people can ask why any of us
are charging for anything.
We have various tools available in our market, some do more than others -
the for-fee ones tend to do more than the free ones, or come with a better
package of services.
- In this case, the for-fee mv.NET has phenomenal support from BlueFinity,
and as a Distributor we try to provide the best tier-1 support experience
we can before taking issues to them. This can't be said with some of the
more static tools.
- mv.NET is constantly being improved - again this can't be said for the
static free tools.
- mv.NET integrates with Visual Studio .NET 2003 and now 2005 - this also
can't be said for any of the other tools except
PDP.NET which isn't
available for jBASE.
- mv.NET has the three libraries that I mentioned in my prior post. That's
one product, three libraries, which means a consistent tool for doing
numerous jobs. You'll need to use various free tools for doing each of the
functions faciliated in mv.NET.
- mv.NET can be used by non-MV developers, people who have no experience
with jBASE. This is a great way to get new people involved with the
environment, and make management happy because it's a lot easier to find a
.NET developer than someone who knows OBjEX or jRCS.
- mv.NET was designed for use with .NET and doesn't require COM Interop
wrappers to make it work, which can be a real problem because most COM/DCOM
components simply weren't designed to work with .NET. There are reasons
for the existence of .NET including the elimination of DLL Hell, and by not
using the proper tools you're not going to derive all of the inherent
benefits.
From a business perspective, sure, our goal at Nebula R&D is to sell
licenses. We want to earn those sales by helping our VARs to succeed. We
do this by providing quality support and product information, access to
education, and assistance with development and marketing. You won't find
this sort of service coming from anyone else in our market, and you almost
certainly don't have a Distributor providing these resources for free
development tools. BTW, as a jBASE Distributor we're gearing up to provide
the same level of services to new jBASE VARs - and of course to end-users.
So yes there is a cost for mv.NET but it's worth it for many reasons as
we've seen in this discussion (including being thread-safe, multi-user
economy, etc). If you have any experience with .NET you'll especially
appreciate the product the more you use it. With a 30 day free evaluation
it can't hurt to give it a try. Contact me for more info or register for
an eval on the BlueFinity web site, and be sure to indicate that you heard
about mv.NET from Nebula R&D - this will ensure you work with us to get our
value-add benefits.
Thanks and Regards,
Tony Gravagno
Nebula Research and Development
TG@ removethisNebula-RnD.com
Clif Bristol wrote:
> Yes isn't that based on concurrent connections? If I have
> 5 concurrent connections then I will need 5 enterprise
> lic and 5 mv.NET lic.
>