Hello,
As you probably know, Compiere uses Oracle as its database. There are
versions in beta that use Sybase or MySQL. I have issues about the
open-ness or lack thereof of Oracle. I also had the task of
supporting
Oracle for running SCT's Banner system, which is a small government /
college oriented ERP-like system. In that instance I was running
Oracle 10 on two Sun
Enterpirse 3500 servers. Just supporting Oracle was a time-intensive
experience,
let alone the rest of Banner. I don't think I would recommend pinning
your business
to either a beta product or a product built on top of Oracle unless
you have at
least one staff full time equivalent you can dedicate to the project
The operant element of the discussion is: small business. If you only
have a
few staff people, then setting up and running Compiere is going to
take a significant
hunk of staff time that you could elsewise be dedicating to making or
supporting
products for your customers.
In our case, Quckbooks is handled by a staff person who is computer
savvy, but not a
software developer. As I pointed out, Quck Books is also a defacto
standard, and it
is easy to find CPAs that have in depth experience with the product,
and can easily
deal with the company books by e-mailing a single file back and forth.
I doubt anybody would run a medium or larger business on Quick Books,
of course.
Perhaps then, you'd want to think about other products, one of which
might be
Compiere. I'd recommend looking at the over-all picture. From a
support point
of view, I sided with a product from Datatel, but the employer picked
Banner. The
IT staff weren't the only people they wanted to satisfy. For whatever
reason, the
accounting department preferred Banner. Maybe they liked COBOL, as
there was
a lot of Microfocus COBOL gluing Banner's modules together.
You have to keep your eye on what your over-all costs will be and how
easy it is
to find people that can continue to run your system when you have
staff turn-over.
Also, consider the ease is of training people or odds offinding people
that already
know the user interface of your system when you have staff turn-over
in your
end-user community. If you are doing business-to-business, you should
consider whether you can do supply chain integration with your
suppliers and
the people you supply. Supply chain integration means you may have to
interface
with Sterling's Gentran Integration Suite, Microsoft Biztalk, etc.
Locally, we
have 1EDISource in Kent that has a product called EDI complete. If
you need
to interface with a large company, you'll likely be exposed to SAP's
communications
module called XI. If you deal with Wal*Mart, you will need to have
the ability to
send and receive data via the AS2 standard (which is S/MIME over
HTTPS).
For a medium to large business, selecting the ERP system is a
complicated
question. I would recommend putting the staffing and traning
questions, and
whether or not you need to integrate your business ahead of the of the
software,
then evaluate open source and commercial products based on the
requirements
criteria you have developed. Also, you may need to look at importing
legacy
data. Finally, there may be differences in how easily various
products may be able
to demonstrate compliance with Sarbanes-Oxley, HIPAA or ANSI business
standards you have to meet.
On Oct 18, 6:31 pm, Scott Mace <
scottym...@gmail.com> wrote:
> Have you actually used any of the packages listed in the article that
> are suggested as enterprise level?
> Saying that Quickbooks is the only viable option is a little over the
> top.
> It looked like some of those had real possibilties, but not having
> used them I have no opinion as to ease of use, but one should not
> dismiss them out of hand.
> Comparing Quickbooks with moneydance is not what should be done.
> Compiere and Quickbooks, how do they stack up?
>
> Scott
>
> >> Using Opera's revolutionary e-mail client:
http://www.opera.com/mail/- Hide quoted text -
>
> - Show quoted text -