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."
Hard to set up?! Never!
Once you get it working, it is not as easy to use as Access anyway. I love OO.org, but I'm not too fond of the database access component. Too bad I don't know C/C++...
Its mentioned in the documentation, but agreed its a pain, and not fully documented, yet.
I think they are waiting until reporting is done to truely 'support' it..
---- Booth was a patriot ----
Sorry, but microsoft doesn't produce a version of MS Office for my linux box.
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?
...all very good but do you get that little odbctest util like you do on Windows?
"I kill you! You no good 56'ing!"
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.
That's "my es cue el", my friend, not "my sequel". This first line has six syllables according to Monty...
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
Joe Barr shows us how to get ODBC, MySQL and OpenOffice to treat each other with respect.
MySQL and ODBC, living together in perfect harmony
They should have called it:
Ebony and Ivory: MySQL, ODBC & OpenOffice 1.0
Ahh yes, is that why some of DB connections where I work are using the "OLE DB for ODBC" drivers?
And if we can get WordPerfect and Word on a Win box to search/find/merge from MySQL and PostgreSQL residing on a Linux box, then we'll all be in heaven.
Mail merge, it's not just for end lusers any more.
first off OLEDB is a lovely technology, much better organised than ODBC, which was good in its day, and serves a very useful purpose being a lowest-common demoninator, but OLEDB is better.
OLEDB *can* run on top of ODBC, but there are native drivers for several commercial dbs out there. No windows programmer would use OLEDB for ODBC when accessing SQL Server for instance.
However, it is MS only, so this post is a little redundant. but just FYI.
it's about respecting the dead.
IIRC, the MS-SQL ODBC driver sits on top of OLEDB. (OLEDB being considered the 'native' driver for MS-SQL.) The realworld performance difference is probably nil.
>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.
It's probably not unknown to those who've use the StarOffice v5.x database ( Adabas = SoftwareAG ). Granted, OO doesn't have the ODBC driver for that free Adabas database but if you've got the SO v5.x CDROM, you've got the driver.
It's working fine here.
BTW, it might not be well known that the database shipped with Sun's StarOffice 5.2( Adabas ) can be run as a multi-client database if you start the server on the right port. Here's a startup script:
x_server -p 7200
sleep 1
x_start dbaseName
sleep 2
xutil -d dbaseName -u control,user-passwd restart
StarOffice and OpenOffice just need to know where the file "./lib/odbclib.so" is. IIRC
LoB
"Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
It's just like Access? So, it's a form builder and a report generator, with full support for embedding standard platform components, including and compliant script engines? Just like Access does?
So, now I can script Open Office applications using Perl, Python, VBScript, JavaScript, and a slew of of less popular languages, just like Access? And I can bring in components built in any of the standard platform development environment, just like Access can use ActiveX controls?
That's incredibly cool. I'm looking forward to trying that.
Or, do you mean it's another crappy, half assed front end that looks superficially similar to Access to someone who's never bothered to use it?
Slashdot is jumping the shark. I'm just driving the boat.
The title is incorrect, please update and then make this posting redundant.
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 wont be happy until I can access my database via DDE ! DDE rulez!
This document has been around forever; I could have sworn that I found it in the first place via Slashdot.
I was looking at it a couple months ago to see if it would make a possible replacement for Access. It appeared that OpenOffice could give a nice frontend for simple forms, but not much beyond that. I didn't want to mess with ODBC, and wasn't about to install MySQL on my work machine.
Access is great for single user desktop applications, but it doesn't really scale that well, even with SQL support.
VB is normally the tool of choice, but I'm caught between the .EXE version becoming obsolete, and our organization not being ready to jump onto the .NET bandwagon.
I'm looking forward to seeing what's new with it in the next OpenOffice release.
I don't know anything about OpenOffice's security model, mind you, so I could be talking rubbish.
connecting OOo with PG via unixODBC was very, very simple. Yes, it involved editing a couple files -- /etc/odbc.ini and odbcinst.ini, but you have templates and you just need to edit them. Of course, you don't even need to edit config files anymore -- use ODBCConfig. It's all there, assuming you do a full RH8 install.
However, I wouldn't be so generous as to say OOo's database capabilities are as good as Access. You can merge print from your database -- that is quite easy. You can edit table structure and data -- OK, but I find phpPgAdmin works better for that. It even has form components and the ability to navigate a database with a form, but personally I haven't mastered this yet and feel it's a bit on the ugly side. Certainly there needs to be better documentation for forms and for the Basic code you may need to put in to automate forms. It also has a visual query designer -- OK.
Overall, OOo's database tools will be useful for some people but it has a ways to go. For forms, I think GNU Enterprise has quite a bit more potential.
I think the nice tihng about Access is that it lets you have SQLish access to a file.
It is self contained, no server, just the application.
There are many simple databases I would like to make, but having to play with some SQLd is annoying.
It's just plain offensive to refer to setting up software as the "Trail of Tears." The Trail of Tears was a time of great suffering of people who were being kicked out of their homeland and decimated with infectious disease. 4000 deaths! Let's at least try to give respect to these innocent humans.
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
Is there any alternative to Microsoft Access? I'm a recent OpenOffice.org convert, but I haven't been able to get shed of MS Office entirely, since I haven't been able to replace MS Access. Am I missing something?
I work for a small business that is just realizing that sometimes a spreadsheet isn't enough. We need a basic desktop database utility, and we need it to be usable by non-developers.
Microsoft Access is the obvious choice, since it is relatively painless to work with. It gives us what we need - creating and modifying tables, editing data, and importing/exporting text files, which checking integrity contraints and data types. The databases we use are all small and for internal use only, so we don't really want to set up a server.
We are in the process of trying to move from MS Office to OpenOffice.org, but this is holding us back. If we can't find a usable Open Source database front end, we'll have to keep shelling out to MS.
Is there an alternative???
Typical lousy security. There's no fundamental reason that MySQL should have to run as root. It'w just a program that accepts incoming connections and reads and writes files. If it needs root privileges, it's broken. Now you've got something else to exploit.
I'm not sure it's fair to query MySQL ABs role in this - did you try accessing Postgres, Interbase, SAPDB, Sybase, MSSQL, Oracle... through OO with unixODBC? Did they work?
Whilst unixODBC sort of works, I've never had much confidence in it - strikes me as being very much the last resort when every other alternative has been tried. In your favour, the MySQL ODBC driver isn't particularly robust - seems to need a number of workarounds to get reliable access from Access (pardon the pun).
I'd also query the quality and reliability of OOs external database support - I've consistently failed to get any database access via JDBC - works fine from my own Java code but never via OO. The documentation was also non-existent last time I looked.
> that secret being the fact that hidden away inside,
> completely unknown to most OpenOffice users, is a
> user-friendly front end for databases
User-friendly? McCreesh was definitely smoking something if he wrote that
StarOffice 6 was as straightfoward as configuring a data source. No harder than doing an external DB connect in Access. OpenOffice is the same thing.
That reminds me -- the database that comes with StarOffice (the name escapes me at the moment) blows goats on all platforms. Next to zero documentation, cryptic as all hell, and did I mention next to zero documentation? If you use StarOffice do yourself a favour and set up a nice Postgres database somewhere. Hell if you use Microsoft Office do the same. I can't believe how tedious it was to try to get the supplied DB running, even on win32.
I hate to break it to you, but MS Access (or free runtime) is the easiest 'app dev platform' I have used on Winbloze.
It is no bullshit to set up(EASY, EASY, EASY!!!).
Development is EASY(Many websites, sample apps a good place to start on various subsystems, books aplenty).
For a small business there is nothing that come even close to reaching the price($800 for copy of Office Developer version, free runtime.)
Developers are growing on trees.
It won't scale well, but the folks that need to can pony up the dough for a db server and some more robust C/S IDE. In the meantime, $800 and cheap consultants can implement all kinds of apps.
I am a java guy(SCJP). I have done quite a bit of PowerBuilder work as well. I love to shittalk on MS AMAP, but Access is more than enough to do most simple projects. Please let me know of any alternative that can come even close to this on Linux, and I'll check it out(believe me, I've been looking).
Win2k/OpenOffice 1.0 user here (/me ducks), so I know my experience doesn't quite apply to the situation at hand . . . Anyway, I set up the mysql odbc driver, and when writing web applications I routinely use OpenOffice to browse around several mysql servers on my intranet by just starting a blank spreadsheet & then clicking "view data sources", where I have added a few data sources which point to the corresponding win2k ODBC DSN's. I just last week dragged a mysql table from the "view data sources" pane into a spreadsheet & saved it as an excel file for a secretary to clean up. When she sends it back, I'll save it as csv & then do a "load data infile blahbhlahblah". It feels like cheating, but heck, it works.
Your "standard platform components" and "compliant script engines" only run under Windows?
Sort of comparing apples to oranges, then.
But I'll agree that it's not Access. At this point, it's more a data browser tool - it hasn't even got a good report generator.
Even as that, it's missing the most important feature of any tool: being able to lock the users out of the application.
Still, not being Access is probably a good thing, since the advice from all my advanced Access instructors has been "Code it in VB."
Yes if you are going to compile stuff yourself you need to be prepared to make sure you actually configure things correctly. So that various software parts agree on where things are located.
/usr/share/libmyodbc/odbcinst.ini /etc/. :)
If you just want to use the damn software on the other hand you simply do:
$ su root
# apt-get install unixodbc libmyodbc openoffice.org unixodbc-bin
# cp
# exit
$ ODBCConfig
- use GUI to configure database info
- note you could skip that 'cp' command and
- config the whole thing here, but that seems
- like extra effort to me when a perfectly good
- MySQL config exists already
$ oowriter
- Tools->Data Sources
- New Data Source
- pick ODBC and the name you set up above
- Do your database stuff...
Not exactly rocket science.
The article author is simply an idiot, who wants to make life difficult by compiling software himself without bothering to configure it properly.
You'll find a few links to explain the
Trail of Tears on my web site.
http://users.netonecom.net/~bbcat/histoire.html
You can use a JDBC driver to get at the data to. It's much easier to set up than ODBC.
You can also export your data to CSV text, or use flat file databses such as xbase.
In fact, I just finished making a java app that converts old foxpro data into CSV, then I merge the data into a form letter and can print labels from the data source.
Everything is there, and easy to set up. The only thing missing is good documentation, IMHO.
For those of you that don't want to go to all of the trouble (not that it's very hard for a sysadmin like myself, but obviously for the author of this article, it was), simply buy a copy of StarOffice 6.0. StarOffice 6.0 comes with a great database program called Adabase that has GUI table design, supports ODBC and MySQL very well. As a matter of fact, from a default install of StarOffice I was able to talk to the MySQL database running on another box immediately just by specifying hostname, port, database name, and username and password for the database.
Worked like a charm, pulled up all my tables in that database and let me add tables, drop tables, add rows, modify rows, delete rows, and basically do anything you could do in a SQL query.
This is really the difference between StarOffice and OpenOffice. Sure they're based on the same code, but Sun has taken the time to make it as easy to use as the MS Office products, and they don't expect their users to be system administrators.
Even if you are a system administrator, how much is your time worth? If it takes 1 or 2 hours of your time to get OpenOffice working properly, wouldn't it be better to just do a 1 hour consulting job instead and buy a copy of StarOffice?
This is something I used to never think about when I was younger, I'd simply spend hours hacking together all the free tools I can find and doing anything to keep from wasting money on something I knew I could get for free. Of course now that I'm getting a little more experienced and older I realize that time is money and that I should probably just buy something that only costs $60 and save myself an hour of my time.
"When the president does it, that means it's not illegal." - Richard M. Nixon
- You can create tables in a database with the GUI, and create queries on those tables.
- You can create tables by dragging from a spreadsheet.
- You can build forms that fire off StarBasic.
- You can generate reports from a database(with 643).
- You can controll OOo from any language via a socket interface.
Plus:A python interface can be found here: PyUno
- It is free.
- You get the source.
- You can use it forever.
I think you can write your own components, but they have to use the OpenOffice GUI layer.-- ac at work
He was refering to his "friend Milt" who was the Windows/DOS/Network guy. This is the person I said shouldn't be trying to install it on Linux. Now if he would have tried on Windows that would have made sense.
The columnist is a linux user and as such figured out the problem and posted the solution. Now how much of a user he is can be debated.
You dont have to be "leet" as you put it to install the equivilent in Linux but it helps to have actually been a user of linux beyond "I installed Suse today".
So if the writer and Milt are the same person I guess you're right. Otherwise reread the article.
Am I missing something?
Yes, Sun's commercial release of OpenOffice.org called StarOffice. That one has all those non-OSS components like a desktop database and spel cheker.
-- ac at work (Again!)
it's offensive because the two things are of totally different proportion. (Frankly, calling Bill Gates a Nazi is the same way.) This article's title is like naming your Cisco Router "The Auswitch" because you don't dig the restrictive interface; or equating the VCR with the Boston Strangler.
The Cherokee Nation had a bicameral legislature, newspapers, and cities. This was a full nation that Andrew Jackson forcibly expelled to Oklahoma. Comparing this ethnic cleansing to one's ODBC setup bugaboos is shit-headed.
Hey, I'm not saying whoever wrote this shouldn't be allowed to say it. But neither should that person be kept from derision, like a darling little prince. Whoever thought up the title of this article is a cockmaster. Deal with it.
"Whatever happened to fair use?"
-- Duff-Man
Especially if you are running a database under Linux, for whatever reason. Say because your budget for a project is a couple hundred bucks (including hardware) and requires the system to generate a lot of paperwork.
"Learning is not compulsory... neither is survival."
--Dr.W.Edwards Deming
Wow, two pages. How about a much more in-depth article with screen shots explaining the whole ! here, accessible from the front page, in the September Journal.It's in postscript format, and 68 pages long with embedded graphics (screen shots).
Those of you running free software can use the simple ps2pdf, or whatever you like to view the Journal. Ten pages covers OpenOffice.org/MySql, and there are other pages covering the Commerce Committee hearing on digital restrictions management/drm (is theft), the free software business demo in NYC, the business demo in Queens, New York, and more exciting stuff can be found at the web site.
NYLXS did an article on this in the September Journal and will be following up with a series on Open Office.
y sq l.html
http://www.nylxs.com/journal/sept2002/openoff_m
http://www.nylxs.com/journal/
http://www.mrbrklyn.com/amsterdam.html http://www.brooklyn-living.com
An example of why GNU will never be mainstream.
A lot of the issues described in the article were caused by the fact that he mixed a compiled MySQL with some rpms. The RPMS from redhat place both the socket and the libraries into different directories. Had he used an RPM to install mysql, it would have been configured for the proper paths. If he had compiled the clients, they would have been looking for files in the default paths as well. If ./configuring an app on a redhat machine it is always a good idea to use --prefix=/usr and then check the paths in the generated Makefile.
I am under attack by a massive army of acronyms! No more! No more!
~ kjrose
However, only half of all SQL Servers are not busy slamming the network, so this post is a little redundant. but just FYI
>:-)
He was refering to his "friend Milt" who was the Windows/DOS/Network guy. This is the person I said shouldn't be trying to install it on Linux. Now if he would have tried on Windows that would have made sense.
The columnist is a linux user and as such figured out the problem and posted the solution. Now how much of a user he is can be debated.
You dont have to be "leet" as you put it to install the equivilent in Linux but it helps to have actually been a user of linux beyond "I installed Suse today".
So if the writer and Milt are the same person I guess you're right. Otherwise reread the article, again.
I use Windows, Solaris, OS 9, OS X, Linux (Redhat currently) and FreeBSD. I don't have time to screw with stuff either and I fully believe Linux is no where near ready for the Desktop.
DreamweaverMX .....
The thing is I don't give a shit. I don't develop Linux, I just use it. And as such it meets my needs. When people want something for nothing they really shouldn't bitch about "useability". If you want ease of use get a Mac. Or hell for that matter get a Windows machine, it's a lot easier to work with than a linux box (especially when his friend Milt is only familiar with DOS, Windows and Networking as I said above).
I am far from a "smug Linux coding wizard" and user friendliness is worth about 2 cents when you're not getting paid for a product. OSS is great in my opinion (i've been using linux since '95) and has come millions of miles from where it was. However, Linux for the desktop is a joke. BTW, buy StarOffice, it comes with a database program which most "Desktop Users" really don't need.
OS X:
Unix-based Desktop
MS Office (actually it's quite nice)
Photoshop
InDesign
Illustrator
FlashMX
Oracle (if it would get out of RC 2)
FileMaker
OS X kicks the shit out of linux as a desktop. Why get a philips-head screw driver for a flat-head job?
The RIGHT TOOL FOR THE RIGHT JOB, it should be common sense. Unfortunately it is far from common and sense left the IT industry in the 90's like a "Bat out of Hades!".
create a free product that is so hard to install/configure/operate/repair that you have to pay for support.
The truth doesn't care what I think.
Sure, it helps. But, ideally, it shouldn't matter that much. Installing Linux is, in the grand scheme of things, a complex enough task that installing a simple bit of office software should be at least as easy.
So if the writer and Milt are the same person I guess you're right. Otherwise reread the article, again.
No, you reread the article:
Note use of the first-person singular "I". That's not "Milt", that's "I".
-- Yoz
Here's the problem. According to the OpenOffice/ODBC howto (dead)linked to by this howto (but still available via google), versions of MySQL after .49 have a 'bug' that causes missing symbol complaints and crashes on the part of OO. (Basically, I think the problem boils down to: The twits at MySQL have managed to break compat. ) The howto thus recommends downgrading to or sticking with Mysql .49. HOWEVER, the latest word from the RedHat advisories indicates that every version of MySQL below, like, .54 is basically an open door for haxx0rs; multiple buffer-overflows in every executable, etc. etc.
So the upshot is that you can pick one of the following:
(1) Have a working database front-end in the form of OpenOffice, or
(2) Have an uncompromised system.
Thanks, Open Source, for wasting two precious hours of my life with a difficult installation procedure that fails because of security vulnerabilities and cross-version incompatibilities!
(Now where's my Office CD again...?)
- undoware.ca
Did anyone else see the sentance:
Powerful words should be used carefully, other wise their glib use leaves our language impoverished and trivialized.
and wonder what g-lib has to do with a conversation on the Trail of Tears? Perhaps I've been coding too long.
In fact, if you want an "Access-like" front end to MySQL, one thing you can do is (gasp) to use Access.
With a MySQL server sitting somewhere on your network, and MyODBC and MS Access on your client machine, you can link the MySQL tables and be able to use Access queries, forms, modules and macros. I'd love it if there were something like Access in the Open Source world, as I find table and query design faster for most things with a visual tool. But until then, Access works just fine as a front end.
No, Thursday's out. How about never - is never good for you?
openoffice and odbc hard????
wtf??
Ive been using OO with sql server, access, and postgresql databases with much luck for many many months.
Possibly ID10T errors ?
this title is as offensive as hell. you people are sick.
Sad to see that it is rather difficult to set things like this us. Reading through some of the comments there seems to be an overwhelming amount bashing going on regarding the skills of the author.
/may not be intimately familiar with all the packages and tools, but
Ok, I admit I know nothing about the author, OpenOffice, and setting up ODBC on Linux. Other than what I have read about it. I have not had to do anything like this for any of my projects, but I may soon. The author needs to be cut some slack. This is just an example of the trouble he went through. Sure he may
things like this need to be ironed out.
This can be seen as more of a reason for standardizing the directory structure of Linux. Sure there are some 'standards' imposed by the various distro's but just about all of them are radically different. Not to mention where things get tossed by default when doing a compile from source. Ok, so Microsoft writes the rules for their OS, then everyone including themselves break it, but there seems to be more companies following these standards rather than not.
---
If these thoughts seems rambling, that's because they are. My mind can't make up it's whether it is coming or going.
Thanks should go to NYLXS, a non-profit organization made up of individuals from the community that provide solutions to small and large business problems of software licensing fees, restrictive code agreements, and abusive auditing tactics.
It was the membership of NYLXS who rented a van and left NYC at 4 am on July 17, 2002 to attend the Commerce Committee "roundtable" on drm, where the odds were stacked against the public at around 22 to 1 according to reporters covering the event. It was individuals within the organization, and friends from other organizations with similar goals, who stood up and said, enough! to the load of bull being put forth by Mr. Jack Valenti and his cronies at that "roundtable". Had it not been for the actions taken on this day, and for the media response, and for the Commerce Committee's damage control (one staff member was quoted as saying "we've never had anything like this happen here before", and the Commerce Committee's damage control response resulting in an invitation to sit down and talk with them, all covered in Newsforge and many other netzine articles), had it not been for NYLXS's actions, the drm legislation was being steamrolled through Congress, and had good momentum. It was stopped in its tracks that day, and the result was it was killed for the year, since the elections came soon after and the legislation was tabled.
Thanks should go to the NYLXS membership who protested Dmitri's imprisonment regularly in NYC while he was imprisoned half way around the world from his home and family.
Thanks should go to NYLXS who are putting on business demonstrations showing that open source works for business. Business demos held in NYC, and in Queens, NY. Business demos that are widely attended. Business demos that are recorded and can be heard at the link above if you download the audio files.
Thanks should go to the NYLXS educational arm, the Free Software Institute, that provides the training to individuals and companies, in open source and free software operating systems, tools, and applications that make individuals more productive, less reliant on others, and provide true cost savings and reliability.
Thanks should go to the members of NYLXS that meet with local legislators both at home in NYC, and in our nation's capitol, and let their views be understood, their voices heard on free and open source software, on the DMCA, on drm, and other relevant issues.
Thanks should go to the members of NYLXS that sacrifice their time, and keep the gears turning behind the scenes to make sure that NYLXS functions as it should, according to its charter.
NYLXS is a non-profit organization that puts earnings from its Free Software Institute back into free and open source software promotion, issues, and problems. Installfests (where you can bring your computer and receive assistance in getting a gnu/linux distribution legally installed on your computer) are just one area where NYLXS members help to promote free and open source software.
While NYLXS can receive donations that are tax-deductible due to its non-profit status, the NYLXS organization prides itself in being doers, not watchers. Membership is open to people who share the organization's ideals and goals, but as stated, this isn't a join and do nothing organization. Members are required to actively participate in the organization. It may take a little while, but normally, new members listen, find some project, issue, mission, within the organization that they like, and then run with it. It is a testament to the diversity of views of the organization that enables such effective and motivated participation on the part of its members. And it is this motivated participation that enables NYLXS to succeed in its mission, and to effectively communicate its message to others curious about what free and open source software is all about.
Thank you NYLXS!
You aren't, or you weren't - AFAIR the RDB project at IBM - System R*? - originally called the language SEQUEL (hence Ingres QUEL, which might be the commercial product someone else remembers).
However the IBM TLA police were called in (they turned a number of products into TLAs for some reason) and officially renamed it S.Q.L., so it's an SQL database these days.
Which is why we over at OSNews had a conversation about what was basically a database over a filesystem. The pieces are there, scattered over different filesystems, from VMS to ReiserFS. Novell,Unix, and Windows. A lightweight database, transparent by workings, but not by power. Why worry about a seperate database, when it's integrated into the system proper?
.Net patent could stifle standards effort
---
Check out Alpha Five from Alpha Software. They've been around since the 80's making DOS and now Win32 software that kicks Access' ass in reviews.
Alpha
I have searched, but I see nothing comparable to MS Access in Open Office.
I think everyone here really has no clue what Access does.
Leo
Which ODBC driver are you using? The one from unixODBC or the one from PostgreSQL?
Oh, get over yourself. At least Red Hat *tells* you that there are security issues with older versions of MySQL. You really think going back to Access gives you better security than using OOo with an "insecure" version of MyODBC?
And "insecure" is in quotes because... out of the security issues Red Hat lists in their errata, I see only one that's client-side, and it's only exploitable if you're talking to a hostile server. The window of opportunity is very small there; almost certainly smaller than what you're exposing yourself to by running MS products, "now with true-color scripting enabled for brighter databases than ever!".
Shame on you slashdot ... Microsoft adds !!!!!!
beuuuarrrrkkkkkkk (puking on my laptop noise) !!!!!
Do you really need to sell you butt to get money that bad ???
Next week it's going to be slashdot.msn.com or what ???
(6) Men employees will be given time off each week for courting
purposes, or two evenings a week if they go regularly to church.
(7) After an employee has spent his thirteen hours of labor in the
office, he should spend the remaining time reading the Bible
and other good books.
(8) Every employee should lay aside from each pay packet a goodly
sum of his earnings for his benefit during his declining years,
so that he will not become a burden on society or his betters.
(9) Any employee who smokes Spanish cigars, uses alcoholic drink
in any form, frequents pool tables and public halls, or gets
shaved in a barber's shop, will give me good reason to suspect
his worth, intentions, integrity and honesty.
(10) The employee who has performed his labours faithfully and
without a fault for five years, will be given an increase of
five cents per day in his pay, providing profits from the
business permit it.
-- "Office Worker's Guide", New England Carriage Works, 1872
- this post brought to you by the Automated Last Post Generator...