[Leaplist] Accouting software - software v. support (and Commerceware v. Hostageware)

[Bryan J. Smith]

William Warren wrote:
> I don't mind telling it to connect if that's what you mean.

Then you either want to:
A)  Bank with a bank that supports industry-standard financial
interfaces/formats, or
B)  Pay for Commerceware and its industry-relationships and support

William Warren wrote:
> make up your mind..
> on one hand it's hostageware..meant to be avoided..then it's worth paying for...

First off, subscribe to Sys Admin and get the free CD of all their
back issues.  Read 2005 January and February which has my 2-part
"Licensing Risks, Not Revolutions" article.  It talks about the
_risks_ of what I call Freedomware, Standardware, Sourceware and
Commerceware -- using a 2-axis, 4-extreme model of open/proprietary
standards/source.

The "open" models are Freedomware, Standardware and Sourceware.
The "closed" model is Commercware, with an off-shoot known as Hostageware.

Understand Commerceware (_not_ Hostageware) can be worth paying for.
Some reasons:
1)  The company maintains long-term compatibility with its own,
proprietary formats
2)  The company provides industry-relations and support that open source cannot

Hostageware is _never_ worth paying for.  Especially because of reason
#1, Hostageware does *NOT* even qualify as "proprietary" because it's
not even compatible with itself over time.  "Proprietary" requires a
company to value its own IP, of which, Microsoft does _not_ value the
formats/interfaces of Office.  Consumers that see and understand this
understand why such Hostageware is to be _avoided_ at all costs.
Hostageware only survives on distribution channel control and
partnerships.

Intuit is Commerceware.  They maintain a fair balance of
compatibility.  They also deliver immense industry partnerships at
their price point, largely due to the economies of scale of their
sheer sales volume.  That means their products are typically worth
their cost, if they are applicable to your business (QuickBooks is
often not for anything beyond a SOHO business).  Intuit also tried and
quickly ended "activation" and other "registration" of its software
after support issues made it more costly -- especially in the bad name
it was giving them.

Considering #2 heavily, if your bank only provides proprietary
interfaces and you have made that selection, then Intuit is your
answer.  You can't stick one foot into the proprietary pond and ask
the community to bail you out.  Which is why I said, if you stick with
the latest Commerceware/Hostageware, understand you will not get much
support out of the community.  But if there is a commercial vendor
that caters to that proprietary system, and they have a proven track
record of delivering volume, that is your best option considering your
choice of bank and its limitations.

There _are_ standard financial interfaces/formats out there.  GNUCash
supports them.  The question is, does your bank?

Understand this is about risks, not revolutions or other ideals.

If you read _every_ one of my posts, I don't talk in "absolutes"
(despite how some may try to demonize what I say).  I intelligently,
logically and methodically point out the "risks" of a selection.  I
sometimes give my preference.  But I also point out when select
Standardware and even Commerceware offer more "value" than Freedomware
or that they might be worth paying for over Freedomware (especially
Standardware that offers full compatibility with a Freedomware
solution).

My mind is quite "made up."  And I apply my logic to every situation.
The problem is, you're not stepping back to look at what your options
_really_ are.  In fact, your entire question is why you're having
issues.  Think _open_standards_ first, _not_ vendor products.

I.e., instead of looking if your bank and seeing if they support
several of the standard financial interfaces, you're asking if it's
"QuickBooks compatible."  That does _not_ tell anyone anything!  What
does your _bank_ support?  That's the question you should ask, and
then ask for something that is compatible.

I call this the "don't ask for scotch tape" problem with Linux users
-- ask for a specific type of tape, let alone not a vendor brand name.

-- 
Bryan J. Smith         Professional, Technical Annoyance
mailto:b.j.smith at ieee.org   http://thebs413.blogspot.com
--------------------------------------------------------
        Fission Power:  An Inconvenient Solution