jonathon wrote:
On Mon, Jan 5, 2009 at 08:38, Ariel Constenla-Haile wrote:
If you are "trying to use Base to run my whole business", I'd recommend not to
create an embedded database (i.e. the data is stored inside an OOo Base file), but to use
a RDBMS like MySQL or PostgreSQL, and Base as a front-end.
The suitablity of Base for running one's business, depends upon what
that business is.
The same is valid if you are using MS Access: no serious person would suggest
you to create a MS Access database for any business use
MS Access is so embedded in corporate America, that Microsoft can't
EOL it. The SOHO market is not the only one that embraced it.
jonathon
If the developers of Base feel as Ariel does, there is no point in even
HAVING Base in OOo. I've never had the opportunity to work with MySQL
or PostgreSQL, so I know nothing about how 'easy' or not they are to
work in. But Access was built (at least in part) for the desktop user
who didn't have a responsive IT department (or ANY IT department) to
depend on.
I'm not a programmer. I'm a bookkeeper. For 24 years I worked in a
very small company, and if I had waited for our one IT guy to develop
what we needed in Foxpro, most of it would never have happened. I
needed a relational database that was easy enough to learn and work in
that I could get systems written and online working on it just 2 or 3
days a month. Foxpro didn't cut it. Access97 did, and that's the
market that I believe OOo Base belongs in.
Maybe Access is flakey when dealing with millions of records. I
wouldn't know. All I ever dealt with was thousands, and for our
purposes it did well. If OOo Base can do as well in that kind of
market, then it will be very useful. If it is designed only with the
professional database programmer in mind, then it will be a failure.
And if HSQLDB is so poor that you can't use Base for serious work
without also getting & learning MySQL, then perhaps the next major push
for OOo Base needs to be replacing HSQLDB with MySQL.
-- Tim Deaton
