Trail of Tears: MySQL, ODBC, & OpenOffice 1.0
Joe Barr writes "
I found a wonderful "how-to" piece called "OpenOffice.org 1.0, ODBC and MySQL," by John McCreesh. In the introduction, McCreesh writes about OpenOffice.org 1.0's "best kept secret" -- that secret being the fact that hidden away inside, completely unknown to most OpenOffice users, is a user-friendly front end for databases that is "a Microsoft Access (and more) equivalent." That may be so, but there is a very good reason why it's a secret: it's too damn hard getting OpenOffice and ODBC wired up correctly."
The "journalist" who wrote the article said his friend was having a hard time getting MySQL, OpenOffice and Linux (Suse) to work. He then lists that his friend can 1) network computers 2) make anything work in DOS and Windows and 3) simply installed the RPMs.
I'm not sure what the hell qualifies this guy to be able to do much of anything in Linux much less tie MySQL to OO via ODBC.
Yes, it may be unknown to most users, but that doesn't mean it's hidden any more than most features in Office.
Anyway, AFAIK a better (non-ODBC) MySQL driver for openoffice.org has been up there on their to-do list for quite some time.
So why not scratch that itch instead?
Install MySQL?
Better get support contract
Config files scattered
ODBC's pow'r
Links data hither and yon
Like many silkworms
Free office software
Fighting forces from Redmond
Freedom is power
Relevant comments
Readers like them, yes they do
Thoughtful minds welcomed
Lame haikus you say?
OK bub, then write your own
Not so easy, huh?
The Trail of Tears was the forced emigration of Native Americans from the South to Oaklahoma. It was brutal and painful, and something that Americans don't like to talk about.
Yeah lets screw open standards.
Admittely ODBC is/was gennerally improved AFAICT by microsoft, it is essentially still an X/Open standard.
It is availble on many platforms, Mac/VMS/Unix/Windows and probably others too. It is a relative striaghtforward C API for database access. Ok, native access could be quicker but I think you'd find difficulty building a thinner layer for all databse engines.
Lets be honest about this two in many cases I reckon you will find OLE DB implement on top of the ODBC drivers . Not that I've ever used OLE DB being a crossplatform developer.
Master of Peng Shui.Ancient oriental art of Penguin Arranging)
Two points:
... how leet should Linux users be before they can install an MS Access equivalent? On Windows, you can do it with a few clicks. It sounds like you want the Linux equivalent to come with a 10-page exam.
1: The writer of the piece, talking about his install troubles, is a Linuxworld columnist. Now, this may not give them kernel-developer-like skills, but...
2:
-- Yoz
Petty nitpicker
You spoiled the joke entirely
I thought it was good.
Modest doubt is called the beacon of the wise. - William Shakespeare
>Are there seriously still people who don't have
>MS Office?
There are projects for which the price of MS Windows and MS Office will preclude the project being done. Such things may not matter to you, since you obviously either have working capital or are willing to compromise your ethics. What if your entire expected revenue was less than the price of that software, but the system you want to develop has value other than cash value? Because of the price of Office, you're suggesting that such a project should not even be done.
That's not your call. It's okay that there are alternatives, and that people choose to use them!
-fb Everything not expressly forbidden is now mandatory.
This certainly isn't the first or last attempt to wrap a user friendly UI on top of MySQL, but I think attempts to push MySQL + a nice GUI as an Access killer are mistaken.
My own experience with Access is fairly limited, but from what work I have done with Access, it seems that the biggest benefit is entirely ignored by this and other products like The Kompany's Data Architect. Access lets you take everything (data, reports, forms, queries, etc) and shove it all into a single portable file. Burning a copy to CD-R or Floppy is a snap, and it seems to be much easier for the clueless to wrap their heads around the idea of a database + reports + forms as a single file. I tried to sell a non-profit organization on the idea of MySQL + custom interfaces as a replacement to their quirky Access databases and they were completely unplussed by the idea.
It seems like such a simple idea to combine perl or Python forms, HTML, XML or PDF reports, and Data into a single gzipped file (maybee even a file that runs on it's own without any third party software other than a perl or python interpriter.) I don't get why so much effort seems to be directed at making MySQL user friendly instead. MySQL seems like complete overkill as an Access replacement. GNutrition is a good example of this problem.. Why in the world do you need a MySQL server for something so simple?
I've seen Amazon reviews pasted into /. for a +5 Informative, but I have to admire your sheer gall in pasting in a comment on the same thread from half an hour ago.
;-).
/. karma a sufficiently precious commodity to bother with this kind of thing...
Good idea, though. This being Slashdot, nobody checks for dupes
Hmm, looks like this is a habit of yours. I'm continually amazed that people consider