> Our organization is considering purchasing RealWorld Visual
> Accounting. It is written in C++ and uses btrieve as its database
> engine. Anyone have any good or bad experiences in using btrieve.
> Is it stable?
I have developed 50+ Btrieve programs with C/C++ and Pascal/Delphi for
the last 12 years, under stand-alone, multi-user, and multi-site applications.
Some programs have run for over 5 years without any complaints or data
corruptions. The few database corruption problems that have occured
(maybe 12 in 12 years) were able to be restored using proper backup
procedures and paper trails. My applications have included several
Personnel systems, customized financial and billing packages, inventory
& accounting systems, and even a complete financial system for a credit
union. (OK, enough back-patting for now).
I would say that Btrieve is one of the fastest, well-designed, and more stable
database programs out there. I use it now despite my opinion that Pervasive
doesn't quite know what to do with it, and that they are pricing it in ways
that I do not like.
However I have seen several applications using Btrieve that flat out SUCK.
They did not put much thought into the design of the databases or indexes;
their user interface is ridiculously complex, there are too many inter-relation-
ships between tables and too many tables (which means that when a corruption
occurs it may be impossible to reliably restore the data without using a back-up
copy, and pray to God one exists), and it takes forever to create simple or
Add to this the fact that in my opinion most Accounting packages SUCK anyway,
no matter what database system they use. I currently run my $9 million (sales)
company using the regular old version Quicken for Windows, and I have
not met any other Accounting package that I would even remotely recommend.
Seeing a poorly-designed package that ignores, abuses or thwarts the speed
and elegance of Btrieve always gets my * boiling, as you may notice.
One of Btrieve's curent weak points is when you mix operating systems (e.g
Win3.1, Win95, WinNT, OS/2, DOS) and especially with the Novell NLM.
Lots of untracable problems seem to start to happen. If the workstations
are all running the same system there is usually no problem.
Quote:> How well does it perform in a client/server configuration?
I have never used the client / server configuration. I prefer to KISS (Keep It
Simple, Stupid) and I do not have any clients that access the same database
from multiple sites, have 500+ users accessing the database at the same time,
or performing heavy SQL, the only reasons for client/server in my opinion.
Quote:> How about usability and performance issues in using their ODBC drivers?
ODBC also SUCKS, it is a kludge created by Microsoft as a marketing ploy.
It only adds another layer to an already over-layered system, and it only
provides a sub-set of some features that Btrieve provides. I currently program
in Delphi, and do not use ODBC; instead I am using Titan which accesses
Btrieve directly, and MUCH faster.
All this of course is my own, highly-biased opinion.