Advantage of Access in corporate environment

[spikepl]

I have to concoct a few lines about the advantages of Access in a corporate environment, and I want to be technically correct. I have seen definitions of Access also on AWF, but cannot find them.

The point I am trying to make is that in a corporate environment, with IT-departments, guidelines, budgets and costcodes, Access can provide a quick and efficient shortcut to a huge amount of database functionality for a small investment of time on part of an enthusiast or two.

And the reasons for this are - PLZ hit me if I am wrong:

1. that the database engine already is part of Windows
2. that Access itself is nothing but a tool to write an interface to interact with the database engine and is often included in the Office installation
3. that an Access database is just one file that does not need to be installed

and from the above follows, that IT-departments have little say in this, that enthusiasts can largely bypass the normal software acquisition procedures in place, drive the IT guys crazy and just get cracking .


Your opinion?

 

[vbaInet]

spikepl, you'll be able to get lots of pros from the Microsoft website and you'll probably get better points.

But in relation to your points:
1. Jet isn't part of Windows. It comes bundled with Access. It's its own data layer.
2. You're selling yourself short on this point. Access is more than a tool, it's an application that allows you to develop a fully functional database system that can be fully integrated with several commercial databases (i.e. Oracle, MySQL, SQL Server and even to the Cloud). Remember it's got an IDE, QBE, Form/Reports Designer, and a database all in one. You could even call it a suite.
3. A bit misleading if you tell them that it's just one file because by the time you deploy, you'll be deploying front ends and a back end. In a dev environment then perhaps this may hold true depending on the setup.

I'll add a few more:
4. Access is fully COM so there's full integration with other COM applications which expose their interface. Don't mention just Office applications because there are so many more out there.
5. If you're looking for a RAD environment, then Access ticks all the boxes. Quick setup, drag and drop features for creating forms and reports, quick and easy deployment (no need for Configuration Management).
6. There's also the web side of things which I've not really looked into much but you could include that.

I'm sure there are few more but I can't think so just go on the MS website and plagiarise.

I can't sing its praises too much but for small/medium sized business it's sufficient.

 

[plog]

Who's your audience? Anyone in IT will roll their eyes and scoff after the first paragraph (which it sounds like you already know). Anyone who has to work with IT (department managers, people who do actual work of the business) will be receptive.

For them I would add these points:

~Step up from the Excel mess that they currently use. When IT finally makes good on their promises to integrate that department's data into the main system it will be an easier transition for IT and in turn the department. Also, when IT brings it into the main system they will have the user interface and reports refined to what they need so IT can just model their work after what the department is used to.

~Maintainability. Access is a widely known tool, so instead of just Excel-guru Sheila being able to troubleshoot issues with the Excel system she built, they will be able to hire someone who knows Access and can get in there and fix the system.

~Integration. If they have Access they probably have the rest of the Suite. You can sell them on creating form letters in Word, dumping datasets to Excel to work with, and integrating it with Outlook to send "automated" emails.

All of those have a fair amount of BS, but its sound logic BS, and really isn't that what this assignment you have is all about?

 

[pbaldy]

I'm no expert, but:

1) JET (mdb) is/was part of Windows, included with MDAC. ACE (accdb) I think is installed with Access.

2) Correct, Access is included with some levels of Office installations. Don't know the end goal, but you may want to mention the free runtime version.

3) Correct, an mdb/accdb is just a file, no install required other than the original Access install (full or runtime).

I agree with your bold paragraph. Too many IT departments are "sure, you need an application that does xyz; we'll put it in the pipeline and you should have it next year". With Access people can create their own solutions. Like any other tool, it isn't right for every job, but it's a great RAD tool (Rapid Application Development).

 

[vbaInet]

I'm no expert, but:

Seriously?

 

[spikepl]

Hmmm.. I am all for all the positives, but such arguments cut no ice in corporate, because its pure gobbledygook to departments heads and most others than IT-people.

The main issue I am dealing with is that normally a software acquisition is subject to a lengthy process and budget, and the resource availability in IT, and so can get killed some time in the next 12 months before someone makes a decision.

All this is bypassed by Access for the reasons I mentioned. I am just trying to verify that that is true (and opinions on whether JET/ACE are/were part of windows are divided - I googled that subject prior to posting).

Ultimately: the specific question I need answered is why is it easier to get Access going compared to a traditional needs-specs-design-test-implementation-disappointment-lamentation-decapitation IT-department governed process.

 

[Galaxiom]

1. Jet isn't part of Windows. It comes bundled with Access.

Jet is part of Windows. It is what Windows uses to mange its own databases. ACE comes with Access from 2007 onward.

 

[vbaInet]

Ultimately: the specific question I need answered is why is it easier to get Access going compared to a traditional needs-specs-design-test-implementation-disappointment-lamentation-decapitation IT-department governed process.

I think I and Paul mentioned the main thing being that it's a RAD tool. And I also mentioned about the fact that you don't need CM (Configuration Management) or EM (Environment Management) involved when it comes to deployment, change management and development.

 

[pbaldy]

Seriously?

The more I learn, the more I realize I don't know.

 

[vbaInet]

Jet is part of Windows. It is what Windows uses to mange its own databases. ACE comes with Access from 2007 onward.

I don't know for sure but I think it was only part of the MDAC at some point but not necessarily part of Windows.

 

[vbaInet]

The more I learn, the more I realize I don't know.

I see why you chose to become a Wino Moderator instead

 

[spikepl]

Thanks guys - I apologize for not beeing clear.

I need the specific arguments that an awake departmental head, tied up in guidelines from head to toe, can use to insist that IT butt out, and counter any arguments concerning IT-safety, or other prospective garbage IT can throw.

(That a self-developed Access application can become mission-critical, and then the author leaves, and then IT says "not our problem", and then the department is in deep doodoo, is another story)

 

[spikepl]

@#11

In Vino Veritas?

 

[vbaInet]

The problem is not all corporate environments are the same. So if you can dish out the sort of arguments that they could bring up we could come up with counter arguments.

 

[Galaxiom]

The ease of getting it going and allowing just anyone to use it can cause major problems.

A colleague previously worked in a government department where Access was used to create all kinds of very poorly designed, undocumented databases that languished when the original developers moved on, causing serious disruption to the processing of data.

They eventually banned it.

 

[pbaldy]

@#11

In Vino Veritas?

Love it!

 

[ButtonMoon]

I suggest you might emphasise the usefulness of Access as a RAD development tool that can integrate with corporate system software e.g. being a lightweight, agile choice of front-end to SQL Server / Oracle. I think that's a more valid corp-friendly use case than the idea of Jet as a "shadow" database system. Jet is really the least attractive feature of the Access package, whereas Access with a SQL DBMS back-end is a much more powerful and flexible proposition.

You can't and shouldn't expect to bypass corporate IT concerns but you can work with them. The CIO is the person who is held accountable for IT systems and digital data in an organisation. If data is unavailable or unsecured or otherwise at risk because it isn't using the supported infrastructure then you might not be held accountable but the CIO most certainly will be - perhaps even in law as well as just internally. So work with that, and bear in mind that working with an established, supported infrastructure probably makes most sense. On grounds of cost and lead time alone, a SQL DBMS fronted with Access can very often deliver much more for less cost than using Access and Jet.