Why do Corporate DB persons hate MS Access

[David W. Fenton]

SQL Server Reporting Services (SSRS) is a very powerful report
design and delivery system. It has drag and drop design, code
behind, graphs and charts, etc. It has built-in scheduling and
subscription capabilities and native output to PDF, Excel and
HTML. SSRS isn't as easy to develop as Access reporting, but it's
an alternative that professional developers should now consider.
It's a free addition to SQL Server.

If your Access app exists for no purpose other than to produce
reports, then that's an alternative that would allow you to switch.

But most apps involve a helluva lot more than just reporting.

And SQL Server has a very good graphical query designer. Some of
the developers on our team prefer it over Access. It isn't
exactly the same, and Access has much better on-the-fly filtering
of the data, but it's a far cry from the old days of typing SQL.

I can't say that I find the SQL Server query designer that great.

I think a lot of the tools in Enterprise Manager were designed based
on the concept of replicating Access's ease of use. They are just
klinkier than Access (though I'm really glad to have them, of
course).

 

[Klatuu]

From a technical perspective, I agree with you.
The dislike for Access/Jet (most don't even know there is a difference) is
not technical based. It is power, control, and ignorance based.

 

[NTC]

also I would say that the title statement is not true that all corporate
DBers hate Access. When I was in there - it is really the issue that our
DBs were so big that Access just wasn't even an issue. Though I do see size
snobbism and understand the statement. We use to export a table of data and
let departments do their own thing...and even suggested they use Access but
they were on their own.... but now that there are these more mature
enterprise wide mining tools like Cognos... I would recommend if the manager
plans to really know the company's data that they learn to use the company's
mining platform if there is one.... Access is a great departmental and
medium/small business product....

 

[Tony Toews [MVP]]

I think it was through your blog, Tony, that I was pointed to this:
http://neopoleon.com/home/blogs/neo/archive/2003/09/29/5458.aspx

Yes, it was on my blog.

Didn't you also post a pointer to a discussion of this topic on your
blog in the last year? I remember going there and adding to the
discussion myself, but can't figure out where it was now.

Quite probably. However the search function on my blog doesn't work.
I should remind the sysadmin.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[orpheusobject]

I have a continuing battle with our database managers. They do not want me to
use MS Access. They're pushing everyone into using Cognos. In my department
we like the flexibility to create ad hoc reports and develop rapid
applications to crunch our data. We also like the ease of integration with
Excel, which is our primary analysis tool. I would appreciate some good
arguments to convince the dB administrators and managers to get off our backs.

It is true that many IT 'professionals' have 'issues' with MS Access -
not the least of which are: potential security holes via MACROS;
linked tables giving sloppy power users unfettered access to back-end
data; and naturally, feeling threatened by a more decentralized
approach to application development by knocking 'experts' out of their
ivory towers by quickly deploying stable and functional applications
not written BY 'experts'.

I would suggest a few main points to stress as counter-arguments:

1) MS ACCESS is a full-featured, RAD tool that, like VB 6.0, .NET,
COGNOS, et al, is only as good as the hands and minds using it. I
don't think it's much of a stretch to note the abject mess that is
legacy COBOL, RPG, or 'C' applications; or, for that matter some web
applications that appear to function as though designed and written by
sexually repressed industrial engineers!

2) MS ACCESS can be locked down, secured, and efficiently coded with a
small client footprint by any professional developer worth their
weight in silicon.

3) MS ACCESS is tightly integrated with other office products (EXCEL,
PROJECT, WORD, ViSio, etc.), AND will literally connect to just about
any data source, including older, odd data sources (DBF, FoxPro, text
files, etc.). This makes interoperability between disparate data-
sources considerably easier than other alternatives, including SQL
Server DTS / SSIS. And this functionality comes out-of-the box with MS
ACCESS.

4) Update queries are extremely easy to write and modify, and can be
easily automated via VBA or MACROS.

5) Timer functionality makes it easy to develop never-ending-programs
that 'wake-up' every so often and perform functions that would be more
difficult using SQL Server or the Windows Scheduler.

7) I think we've already touched upon the ease of prototyping, design,
and development of some pretty impressive-looking reports.

8) Even though there is widely varying levels of skill amongst ACCESS
programmers, one can procur an ACCESS programmer for less money than
a .NET or C++ developer. This argument should make the bean counters
salivate

10) One can employ unbound and 'connect-as-needed' techniques and
methods to create ACCESS applications that are lean, mean, and do not
maintain costly constant connections to a back-end data-base.

11) Most other techniques associated with client-server and web-based
development may be applied to ACCESS applications, e.g, pass-thru
queries, stored procedures, database triggers, UDF's, etc. The only
limits are the skill and imagination of the programmer.

12) Using royalty-free run-time support of the office developers
tools / edition (ODE) of ACCESS, a company need only purchase one to a
few licensed copies of ACCESS and ONE copy of ODE. The application can
be packaged and deployed to an unlimited number of clients (like any
other dev tool), and they do not have to have the ACCESS product
installed on the target client.

I hope this helps!

~Michael

 

[Tony Toews [MVP]]

10) One can employ unbound and 'connect-as-needed' techniques and
methods to create ACCESS applications that are lean, mean, and do not
maintain costly constant connections to a back-end data-base.

What do you mean by "costly constant connections"?

12) Using royalty-free run-time support of the office developers
tools / edition (ODE) of ACCESS, a company need only purchase one to a
few licensed copies of ACCESS and ONE copy of ODE. The application can
be packaged and deployed to an unlimited number of clients (like any
other dev tool), and they do not have to have the ACCESS product
installed on the target client.

With A2007 the runtime is a free download.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/