Dan
If your IT department says don't use Access for databases, it's because they
don't know how to properly develop an Access database. Splitting is the answer.
The data in aback end rarely becomes unstable. But unless you have proof they
won't listen to you. That's a decent article you linked. If you can get the lead
IT person to read it and discuss it with you, you might be able to convince him
that Access is okay to use...as long as the data does not have to be secured.
Compromise and build the back end in SQL Server. If money is an issue, use SQL
Server Express. It's free and has all the tools you will need to build your
tables. Plus it has the security and stability of SQL Server Standard edition.
You can even build your tables in Access and then use SQL Server Migration
Assistant for Access to upsize the back end.
Regards,
Bill Mosca,
Founder, MS_Access_Professionals
That'll do IT <http://thatlldoit.com/> http://thatlldoit.com
MS Access MVP
<https://mvp.support.microsoft.com/profile=C4D9F5E7-BB03-4291-B816-64270730881E>
https://mvp.support.microsoft.com/profile=C4D9F5E7-BB03-4291-B816-64270730881E
My Nothing-to-do-with Access blog
<http://wrmosca.wordpress.com> http://wrmosca.wordpress.com
From: MS_Access_Professionals@yahoogroups.com
[mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Dan Abc
Sent: Saturday, December 01, 2012 6:39 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] IT suggests not to use MS Access
At work our IT is suggesting not to use MS Access because the data base is prone
to corruption, is that true?
the data bases that I made are small and still work fine after 2 years
http://www.techrepublic.com/blog/10things/10-reasons-why-it-pros-hate-microsoft-
access-but-really-shouldnt/386
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (3) |
Tidak ada komentar:
Posting Komentar