Well said! As IT professionals and custodians of the most precious
asset our companies own it is imperative that we continue to move toward
uses of corporate data that are controlled, documented and tested. MS
Access development typically fails on all three of those facets.

Mike


-----Original Message-----
From: Jeremy Greaves
[mailto:mssqldba-ezmlmshield-x58332366.[Email address protected]
Sent: Monday, July 30, 2007 4:13 PM
To: LazyDBA Discussion
Subject: RE: Using Access to create reports and queries to a SQL server


Also...
MS-Access databases and user created applications (MS-Access entities
that
are not merely databases and includes forms and reports, referencing
"internal" or externally linked tables, or views), also have a tendency
of
being cloned and then will mutate depending upon the needs of the new
user.
This is guarunteed to cause a headache to the DBA who will inevitably
have
to get involved as there is a misconception that MS-Access app's are
databases, or access corporate databases and therefore are within the
domain
of the SQL or Oracle DBA.
Each "application" will probably connect to the SQL datasource with the
original users Username and Password, and will have diverged from the
original in that new reports, queries, and macro's will have been
developed
to augment the existing function.
I have lost count how many times I have had to trot over to a Power User
or
"Developers" cube/office to extract them from a mishandled ODBC
definition
('cos they're too lazy to remember how to access the ODBC DSN) or an
application/database that was originally developed by someone that knew
what
they were doing, left the company handing the application/database to
someone that didn't know what they were doing, who left and handed it to
yet
someone else that doesn't know what they are doing but have to get a
report
to higher management by the end of the day!!!!

Like cockroaches, once you let an MS-Access DB/App into the user
community,
before you know where you are you'll have dozens of them... all similar
but
no longer the same.

I worked at a place where it took almost a year to get all their
MS-Access
DB's Y2K compliant, that's how many there were, and there were 3-4 of us

doing it, full time!!!!!

Jeremy Greaves
Fenris Software Consulting, Inc



>From: "Norkett Margaret "
><mssqldba-ezmlmshield-x99807782.[Email address protected]
>To: "LazyDBA Discussion" <[Email address protected]
>Subject: Using Access to create reports and queries to a SQL server
>Date: Mon, 30 Jul 2007 14:25:31 -0400
>
>I have a developer here who LOVES to use MS Access to create queries
and
>reports in. She links tables from my SQL2005 database in it and goes to
>town. I know I've read on this forum that there is a performance hit
>involved with this practice (I think), so would like to take
information to
>my boss to help him discourage her from this practice.
>
>
>
>What say ye?
>
>
>
>If you have any questions or concerns, please let me know them.
>
>
>
>Margaret Norkett
>
>Database Administrator
>
>* 864-271-6522 ext 222
>
>* 864-270-2884
>
>
>
>
>
>
>
>
>
>Experience is the name everyone gives to their mistakes.
>
>Oscar Wilde <http://www.quotationspage.com/quotes/Oscar_Wilde/> , Lady
>Windermere's Fan, 1892, Act III
>Irish dramatist, novelist, & poet (1854 - 1900)
>
>~
>
>
>
>
>
>---------------------------------------------------------------------
>TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
>To post a dba job: http://jobs.lazydba.com
>To subscribe : http://www.LazyDBA.com
>To unsubscribe: http://www.lazydba.com/unsubscribe.html
>




---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html


MS Sql Server LazyDBA home page