I have been around business schools a fair bit and have noticed a few disturbing trends. For one, it seems that the majority of undergraduate business programs include at least one core course involving Microsoft Access. Sometimes Access is taught in labs or tutorials outside regular class, but the question remains, why?
I have received two answers to this question:
These answers are bullshit.
First, “fundamentals of database” includes at least two things. The first is database design. The second is SQL. If the B-Schools are teaching fundamentals of database, why in the hell are their students using Access’s proprietary query builder instead of writing SQL, and what is this bullshit about Access’s “forms” and “reports.” You won’t see this crap in Oracle, DB2 or MySQL. Furthermore, I haven’t seen much education on database design in these intro classes, and assignments rarely include design activities because they can’t be graded quickly.
Second, I can’t find a shred of evidence that Access is heavily used. I don’t know anyone who uses Access professionally. A quick search on Craigslist (Vancouver) brought up 95 jobs requiring Oracle, 122 jobs involving SQL Server, 157 jobs involving MySQL and 7 jobs involving MS Access.
So, my question remains… why does it seem like most schools are teaching not only Access, but also the proprietary wizards and features of Access?
| Comments | Published in | PREV | NEXT |
|---|---|---|---|
| 7 |
education essay information technology |
It’s easy – like you pointed out – easy to grade too. An MS Access license is a lot cheaper than a dedicated server and an SQL license although, for educational purposes, Postgresql and MySQL are probably free. I suspect the instructors themselves might not know SQL.
Teaching CREATE TABLE and SELECT . . . FROM . . . WHERE . . . even at the most basic level is harder than handing someone Access and saying, “This is essentially what databases are about.”
Most of the “business people” (MBA’s, Six Sigma Black Belts) where I work use MS Access exclusively for their data needs. A handful of the sharper ones actually use MSSQL – and boy, do they have a leg up on their peers!
Information Services people and Operations geeks like me do most of the keyboard based SQL, though.
You’re right, it is BS. To get beyond that you’ve got to learn SQL on your own – usually in the workplace.
MS pays schools to use and teach their software. Simple as that.
For people who know nothing about databases, Access is a fine place to start. They will learn the concept of normalizing data, relating tables and even if they are not writing the SQL, you can teach how a language is required manipulate the data. People in business school will never be programming on Oracle databases, but understanding the concepts will help them talk to technologists. As a business analyst or technologist, having your users grasp some idea is a blessing!
Access does seem somewhat antiquated, but I’m not sure if there is another solution that provides a level of abstraction.
Also
Tons of HR people in my company use access to manipulate data and run ad hoc reports. Granted, IT would rather build robust reporting soluitions for them like Business Objects, but it is something they can pick up and use to get what they need.
I understand the programmer/dba pain with Microsoft Access, I really do. We had customers using Access databases and when it comes down to it if you really do your legwork, you will realize when the day is over that JETSQL is actually pretty damned amazing. For what it is, it offers users interested in business the tools in a box to get business done. On the other hand, yes they can get more done after designers, archtiects, programmmers, program managers, finance, executive teams and such get together, inflate their self worth, their pay, and titles for developing a system on Oracle, Business Objects and SAP. Is it worth it?
If it gets the job done and if it is efficient, perhaps learn from the prototype that the user developed in Access to scale up to a larger solution. I really don’t see a problem with Access, it’s a business man’s rapid prototyping tool. Everyone wants to justify thier job position, cry babies.
@infixum,
I think that showing a business student access and saying, “here, this is what databases are about,” is sort of like handing an aerospace engineer a paper airplane and saying “here, this is what space shuttles are about.” It isn’t a straightforward introduction, it’s a dangerous lie.
@H, MS does not pay either of the business schools I am familiar with to use Access. It wouldn’t surprise me if they did, but I’m not aware of them actually doing it.
@linzc111, No, Access is not a fine place to start because it’s not a simple database – it’s completely unlike any full-featured DBMS. This is not the same as teaching people the basics of flying in a Cesna because it’s simpler than a jumbo jet. Access isn’t simpler, it’s different. Playing with Access doesn’t teach students the basics of databases, it teaches them the intricacies of the Access interface. Teaching query-by-example and Access’s peculiar take on forms and reports is a complete waste of time.
@lycanr1,
My problem with access isn’t with using it to facilitate prototyping in some end-user design project, it’s with misleading students about the nature of databases by using it as a teaching tool.
I am not a programmer and appreciate the need for databases. Growing weary over the years of endless meetings with programmers explaining what the database I need is supposed to accomplish (“I’m sorry I just don’t understand why you need to see the name of the customer here”), I now create my own when I need one.
Access is simple. It gets the vast majority of database tasks done without having to address all the annoyances of databases. Relying on SQL is not better (and yes I can write SQL statements). It is a pain in the neck. The Access query builder is very strong because it is proprietary. All the more-power-and-control-arguments do not stack up against ease of use, something Mr. Wolfe pointed out in another blog post. If Microsoft had worked out the incompatibility of versions problems, the terrible record locking and poor performance on the internet we wouldn’t be discussing anything else.