Slashdot Mirror
MS Unveils Office 2007, Multiple Versions
rfunches writes "MSNBC reports that Microsoft's next version of Office, now known as Office 2007 (previously code-named Office 12), will continue targeting the corporate audience through multiple versions of Office 2007. Versions announced include 'Office Professional Plus 2007' and 'Office Enterprise 2007.' From the article: '[Microsoft Office Professional Plus 2007] will integrate capabilities of SharePoint, a collaboration program and Web portal that is designed to run over corporate networks and the Internet...and also incorporate Microsoft Office Communicator, a corporate instant messaging service.'"
one what? A database?
Surely you jest. Access is not the best solution out there--it is horrible to use, the interface just blows, and it doesn't do a lot of what it should do. For the record OOBase Sucks as well.
Now that I have used MSSQL more, I am realizing the power of such a database. At work we are also getting ready to implement Crystal Reports, which makes the reporting components in Access look anemic and pathetic.
I am not a big MS fan, but I do think that they make a fine SQL server.
Folks, don't use Excel as a db, but access shouldn't be used either!
"We don't know what we are doing, but we are doing it very carefully,..." Wherry, R.J. Personnel Psychology (1995)
All recent versions of Microsoft Access are able to actually use the desktop version of SQL server instead of the old JET-based engine.
Look up "access data project" in the Access help file. You can make it the default DB type, and most features of the "real" SQL Server are available (except the GUI management tools).
I am probably one of the biggest Linux Fanboys out there, I am not afraid to admit it. And I love to bash on MS.
But when I get serious and talk "right tool for the right job" I would heartily disagree with your feelings about Access.
I began my career in IT on Access (V. 1.1, Win 3). I've loved it ever since. I write all sorts of automation solutions for our company in Access. We use Great Plains and I've saved the company thousands of dollars by creating little, even somewhat crappy, automation routines in Access instead of buying some bloated module for GP that does way more then we need it to. It's quick, easy and gets the job done.
Access and ODBC let me connect to any database I want. I have our web site scp a snapshot of our MySQL databases to a local test copy of the web site. And I use Access to connect to it and run quick & dirty reports and queries. You like SQL Server but Access is not a substitute for MSSQL, it's a compliment to it. You can connect to SQL using Access. I tend to start my projects first in Access so I can carry it around with me while I develop it. When I feel the project is ready for a first release it is very easy to upload all my tables, data and queries to SQL Server and simply link in the new tables. No need to change my forms, reports or code because the linked tables are named the same, they just reside in a more robust and scalable database now that they are deployed.
Access's interface does take some getting used to and VBA is not a Real(TM) programming language but the beauty of VBA is, if you don't like the Access interface, change it using VBA. When I finish an automation solution that keeps some poor SOB in my company from typing the same data into our systems day in and day out the interface he/she uses is far different then that of standard Access.
Bottom line is, it's all about using the right tool for the job and for the small company I work for Access is the right tool in some very key situations.
P.S. I realize there are 100's, if not 1000's of other solutions that do similar things to what I describe above. My company owned Access and MSSQL so that and my familiarity with Access led to my choice.
Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal