Editing Microsoft Access (section)

==History==

In the 1980s, Microsoft Access referred to an unrelated telecommunication program that provided terminal emulation and interfaces for ease of use in accessing online services such as [[Dow Jones News/Retrieval|Dow Jones]], [[CompuServe]] and electronic mailbox.<ref>{{Cite book|url=https://books.google.com/books?id=Wcv9oIHOrjQC&pg=PA139|title=PC Mag|date=October 15, 1985|publisher=Ziff Davis, Inc.|language=en}}</ref><ref>{{Cite web|title=Microsoft Access Business Information Access Program 1.0x|url=https://winworldpc.com/product/microsoft_access_business_information_access_program/10x|access-date=May 23, 2022|website=WinWorld}}</ref>

With the popularization of personal computing at home and in the workplace, in the 1990s desktop databases became commonplace.<ref>{{Cite journal |date=1990 |editor-last=Blaser |editor-first=Albrecht |title=Database Systems of the 90s |url=https://link.springer.com/book/10.1007/3-540-53397-4 |journal=Lecture Notes in Computer Science |language=en |doi=10.1007/3-540-53397-4 |issn=0302-9743}}</ref> Prior to the introduction of Access, [[Borland]] (with [[Paradox (database)|Paradox]]), [[Ashton-Tate]] (with [[dBase]], acquired by Borland in 1991) and Fox (with [[Visual FoxPro|FoxPro]]) dominated the desktop database market. Microsoft Access was the first mass-market database program for Windows. With Microsoft's purchase of FoxPro in 1992 and the incorporation of Fox's Rushmore [[query optimization]] routines into Access, Microsoft Access quickly became the dominant database for Windows—effectively eliminating the competition which failed to transition from the [[MS-DOS]] world.<ref>{{cite web |title=Microsoft Access History |url=http://www.fmsinc.com/MicrosoftAccess/history/index.html |access-date=March 13, 2016}}</ref>

===Project Omega===

Microsoft's first attempt to sell a [[relational database]] product was during the mid-1980s, when Microsoft obtained the license to sell [[R:Base]].<ref name=Goodhew1996-11>{{cite web|title=Jet Engine: History|author=Goodhew, Tony|year=1996|url=http://www.avdf.com/nov96/acc_jet.html|access-date=January 2, 2011}}</ref> In the late 1980s Microsoft developed its own solution codenamed Omega.<ref name=FergusonBirth>{{cite web|title=The Birth of Visual Basic|author=Ferguson, Scott|url=http://www.forestmoon.com/birthofvb/birthofvb.html}}</ref> It was confirmed in 1988 that a database product for Windows and [[OS/2]] was in development.<ref>{{Cite news|title=Microsoft Works on SAA Database|first1=Mark|last1=Brownstein|first2=Stuart J.|last2=Johnston|newspaper=InfoWorld|date=November 14, 1988|page=5|url=https://books.google.com/books?id=wTsEAAAAMBAJ}}</ref><ref>{{Cite news|title=Microsoft Puts Finishing Touches on Windows Applications|first=Mark|last=Brownstein|newspaper=InfoWorld|date=February 13, 1989|page=5|url=https://books.google.com/books?id=QDoEAAAAMBAJ}}</ref> It was going to include the "EB" Embedded Basic language,<ref name="FergusonBirth"/> which was going to be the language for writing macros in all Microsoft applications,<ref>{{Cite news|title=Microsoft Applications to Share Macro Language|first=Laurie|last=Flynn|newspaper=InfoWorld|date=May 8, 1989|page=1|url=https://books.google.com/books?id=RzoEAAAAMBAJ}}</ref> but the unification of macro languages did not happen until the introduction of [[Visual Basic for Applications]] (VBA). Omega was also expected to provide a front end to the [[Microsoft SQL Server]].<ref>{{Cite news|title=Microsoft Waits on SQL Front Ends|first=Laurie|last=Flynn|newspaper=InfoWorld|date=August 21, 1989|page=109|url=https://books.google.com/books?id=rjAEAAAAMBAJ}}</ref> The application was very resource-intensive, and there were reports that it was working slowly on the [[Intel 80386|386]] processors that were available at the time.<ref>{{Cite news|title=Gates Claims That 80286 Systems Are No Longer His Babies|first=Robert X.|last=Cringely|newspaper=InfoWorld|date=September 4, 1989|page=82|url=https://books.google.com/books?id=rDAEAAAAMBAJ}}</ref> It was scheduled to be released in the 1st quarter of 1990,<ref>{{Cite news|title=No Way, the PC Industry Will Always Be Dominated By Doritos|first=Robert X.|last=Cringely|newspaper=InfoWorld|date=July 31, 1989|page=86|url=https://books.google.com/books?id=tjAEAAAAMBAJ}}</ref> but in 1989 the development of the product was reset<ref name="Goodhew1996-11"/><ref>{{Cite news|title=Lotus Exec Tells of Ordeal: "Aliens Force Me to Use MS Windows"|first=Robert X.|last=Cringely|newspaper=InfoWorld|date=October 16, 1989|page=106|url=https://books.google.com/books?id=nDAEAAAAMBAJ}}</ref> and it was rescheduled to be delivered no sooner than in January 1991.<ref>{{Cite news|title=Elvis, Now a Vegas Parking Lot Attendant, Further Delays Intel 486|first=Robert X.|last=Cringely|newspaper=InfoWorld|date=November 20, 1989|page=106|url=https://books.google.com/books?id=qDAEAAAAMBAJ}}</ref> Parts of the project were later used for other Microsoft projects: Cirrus (codename for Access) and Thunder (codename for [[Visual Basic]], where the Embedded Basic engine was used).<ref name=Goodhew1996-11/><ref name=FergusonBirth/> After Access's premiere, the Omega project was demonstrated in 1992 to several journalists and included features that were not available in Access.<ref>{{Cite news|title=Microsoft demos its ill-fated Omega|first=Scott|last=Mace|newspaper=InfoWorld|date=November 30, 1992|page=16|url=https://books.google.com/books?id=L1EEAAAAMBAJ&pg=PA16}}</ref>

===Project Cirrus===

After the Omega project was scrapped, some of its developers were assigned to the Cirrus project (most were assigned to the team which created Visual Basic).<ref name="Goodhew1996-11"/> Its goal was to create a competitor for applications like [[Paradox (database)|Paradox]] or dBase that would work on Windows.<ref>{{Cite news|title=Microsoft's Fox purchase stirs up the XBase market|first1=Lisa|last1=Picarille|first2=Scott|last2=Mace|newspaper=InfoWorld|date=March 30, 1992|page=1|url=https://books.google.com/books?id=5j0EAAAAMBAJ|quote=Cirrus (...) will go head-to-head with Paradox and Metaphor Computer Systems' Metaphor program.}}</ref> After Microsoft acquired [[FoxPro 2|FoxPro]], there were rumors that the Microsoft project might get replaced with it,<ref>{{Cite news|title=Whatever costume Eckhard wears is likely to scare Silicon Graphics|first=Robert X.|last=Cringely|newspaper=InfoWorld|date=November 4, 1991|page=118|url=https://books.google.com/books?id=Xz0EAAAAMBAJ|quote=(...) rumor (...) that FoxPro might replace Redmond's long-delayed database, now code-named Cirrus.}}</ref> but the company decided to develop them in parallel. It was assumed that the project would make use of [[Extensible Storage Engine]] (Jet Blue)<ref>{{Cite news|title=Microsoft creating API to complement ODBC|first=Scott|last=Mace|newspaper=InfoWorld|date=June 29, 1992|page=1|url=https://books.google.com/books?id=blEEAAAAMBAJ|quote=Open ISAM support will be in Microsoft's forthcomming Cirrus DBMS for Windows.}}</ref> but, in the end, only support for [[Jet Database Engine]] (Jet Red) was provided. The project used some of the code from both the Omega project and a pre-release version of Visual Basic.<ref name="FergusonBirth"/> In July 1992, betas of Cirrus shipped to developers<ref>{{Cite news|title=Developers get beta version of Microsoft DBMS|newspaper=InfoWorld|date=July 13, 1992|page=3|url=https://books.google.com/books?id=elEEAAAAMBAJ}}</ref> and the name Access became the official name of the product.<ref>{{Cite news|title=Cirrus dubbed Access; faster beta released|newspaper=InfoWorld|first=Stuart J.|last=Johnston|date=July 20, 1998|page=1|url=https://books.google.com/books?id=IlEEAAAAMBAJ}}</ref> "Access" was originally used for an older terminal emulation program from Microsoft. Years after the program was abandoned, they decided to reuse the name here.<ref>{{cite web|url=https://devblogs.microsoft.com/oldnewthing/20060413-09/?p=31543|title=Where did the name for Microsoft Access come from?|publisher=Microsoft|work=The Old New Thing|date=April 13, 2006|access-date=March 13, 2016}}</ref>

===Timeline===
[[File:Microsoft Office Access (2000–03).svg|thumb|89x89px|Access' logo for [[Microsoft Office 2000|Office 2000]] and [[Microsoft Office XP|Office XP]]]]
Microsoft released Access version 1.0 on November 13, 1992, and an Access 1.1 release in May 1993 to improve compatibility with other Microsoft products and to include the Access Basic programming language.

With Access v2.0, Microsoft specified the minimum hardware requirements to be Microsoft Windows v3.1 with 4&nbsp;MB of [[Random Access Memory|RAM]] required, 6&nbsp;MB RAM recommended; 8&nbsp;MB of available [[hard disk]] space required, 14&nbsp;MB hard disk space recommended. The product shipped on seven 1.44&nbsp;MB diskettes. The manual shows a 1994 copyright date.

As a part of the Microsoft Office 4.3 Professional with Book Shelf, Microsoft Access 2.0 was included with first sample databases "NorthWind Trader" which covered every possible aspect of programming a database. The Northwind Traders sample first introduced the Main Switchboard features new to Access 2.0 for 1994.

With Office 95, Microsoft Access 7.0 (a.k.a. "Access 95") became part of the Microsoft Office Professional Suite, joining Microsoft Excel, Word, and PowerPoint and transitioning from Access Basic to VBA. Since then, Microsoft has released new versions of Microsoft Access with each release of Microsoft Office.<ref>{{cite web|url=https://www.fmsinc.com/microsoftaccess/history/versions.htm|title=Microsoft Access Version Releases, Service Packs, Hotfixes, and Updates History|publisher=FMS|access-date=August 20, 2023}}</ref>

Versions 3.0 and 3.5 of [[Jet Database Engine]] (used by Access 7.0 and the later-released Access 97, respectively) had a critical issue which made these versions of Access unusable on a computer with more than 1&nbsp;GB of memory.<ref>[http://support.microsoft.com/kb/161255 "Out of memory" error starting Microsoft Access]</ref> While Microsoft fixed this problem for Jet 3.5/Access 97 post-release, it never fixed the issue with Jet 3.0/Access 95.

The native Access database format (the Jet MDB Database) has also evolved over the years. Formats include Access 1.0, 1.1, 2.0, 7.0, 97, 2000, 2002, and 2007. The most significant transition was from the Access 97 to the Access 2000 format; which is not [[Backward compatibility|backward compatible]] with earlier versions of Access. {{as of|2011|post=,}} all newer versions of Access support the Access 2000 format. New features were added to the Access 2002 format which can be used by Access 2002, 2003, 2007, and 2010.

Microsoft Access 2000 increased the maximum database size to 2&nbsp;GB from 1&nbsp;GB in Access 97.

Microsoft Access 2007 introduced a new database format: ACCDB. It supports links to [[SharePoint]] lists and complex [[data type]]s such as multi-value and attachment fields. These new field types are essentially recordsets in fields and allow the storage of multiple values or files in one field. Microsoft Access 2007 also introduced File Attachment field, which stored data more efficiently than the [[Object Linking and Embedding|OLE (Object Linking and Embedding)]] field.
[[File:Microsoft Access 2013-2019 logo.svg|thumb|89x89px|The logo for Access from 2013 to 2019]]
Microsoft Access 2010 introduced a new version of the ACCDB format supported hosting Access Web services on a [[SharePoint]] 2010 server. For the first time, this allowed Access applications to be run without having to install Access on a user's PC and was the first support for Mac users. Any user on the SharePoint site with sufficient rights could use the Access Web service. A copy of Access was still required for the developer to create the Access Web service, and the desktop version of Access remained part of Access 2010. The Access Web services were not the same as the desktop applications. Automation was only through the macro language (not VBA) which Access automatically converted to JavaScript. The data was no longer in an Access database but SharePoint lists. An Access desktop database could link to the SharePoint data, so hybrid applications were possible so that SharePoint users needing basic views and edits could be supported while the more sophisticated, traditional applications could remain in the desktop Access database.

Microsoft Access 2013 offers traditional Access desktop applications plus a significantly updated SharePoint 2013 web service.<ref>{{cite web|url=http://msdn.microsoft.com/en-us/library/office/jj618413.aspx|title=Changes in Access|publisher=Microsoft|access-date=March 13, 2016}}</ref> The Access Web model in Access 2010 was replaced by a new architecture that stores its data in actual SQL Server databases. Unlike SharePoint lists, this offers true relational database design with referential integrity, scalability, extensibility and performance one would expect from SQL Server.<ref name="New in Access for developers">{{cite web|url=http://msdn.microsoft.com/en-us/library/office/jj250134.aspx|title=New in Access for developers|publisher=Microsoft|access-date=March 13, 2016}}</ref> The database solutions that can be created on SharePoint 2013 offer a modern user interface designed to display multiple levels of relationships that can be viewed and edited, along with resizing for different devices and support for touch. The Access 2013 desktop is similar to Access 2010 but several features were discontinued including support for Access Data Projects (ADPs),{{clarify|date=January 2021}} pivot tables, pivot charts, Access data collections, source code control, replication, and other legacy features.<ref>{{cite web|url=http://office.microsoft.com/en-us/access-help/discontinued-features-and-modified-functionality-in-access-2013-HA102749226.aspx|title=Discontinued features and modified functionality in Access 2013|publisher=Microsoft|access-date=March 13, 2016}}</ref> Access desktop database maximum size remained 2&nbsp;GB (as it has been since the 2000 version).

Microsoft Access is no longer included in the one-time-purchase version of [[Microsoft Office 2021]], but remains within the [[Microsoft 365]] counterpart, as Apps for business and Business Standard editions. Features new to Access 2021 include an extended-precision date/time data type<ref>{{cite web|url=http://support.microsoft.com/en-us/office/using-the-date-time-extended-data-type-708c32da-a052-4cc2-9850-9851042e0024|title=Using the Date/Time Extended data type}}</ref> and dark theme support.<ref>{{cite web|url=http://support.microsoft.com/en-au/office/what-s-new-in-access-2021-2c5c0766-b22b-4b81-a222-a791a8b5b54b|title=What's new in Access 2021}}</ref>

In addition to using its own database storage file, Microsoft Access also may be used as the 'front-end' of a program while other products act as the 'back-end' tables, such as [[Microsoft SQL Server]] and non-Microsoft products such as [[Oracle database|Oracle]] and [[Sybase]]. Multiple backend sources can be used by a Microsoft Access Jet Database (ACCDB and MDB formats). Similarly, some applications such as [[Visual Basic]], [[ASP.NET]], or Visual Studio .NET will use the Microsoft Access database format for its tables and queries. Microsoft Access may also be part of a more complex solution, where it may be integrated with other technologies such as [[Microsoft Excel]], [[Microsoft Outlook]], [[Microsoft Word]], [[Microsoft PowerPoint]] and [[ActiveX control]]s.

Access tables support a variety of standard field types, [[Index (database)|indices]], and [[referential integrity]] including cascading [[Update (SQL)|updates]] and [[Delete (SQL)|deletes]]. Access also includes a [[Information retrieval|query]] interface, forms to display and enter data, and reports for printing. The underlying [[Access Database Engine|Access database]], which contains these objects, is [[multi-user]] and handles [[Lock (database)|record-locking]].

Repetitive tasks can be automated through macros with [[point and click]] options. It is also easy to place a database on a network and have multiple users share and update data without overwriting each other's work. Data is [[Lock (database)|locked]] at the [[Row (database)|record]] level which is significantly different from Excel which [[Lock (computer science)|locks]] the entire spreadsheet.

There are [[template (file format)|template]] databases within the program and for download from Microsoft's website. These options are available upon starting Access and allow users to enhance a database with predefined tables, [[query language|queries]], forms, reports, and macros. Database templates support [[Visual Basic for Applications|VBA]] code, but Microsoft's templates do not include VBA code.

Programmers can create solutions using VBA, which is similar to [[Visual Basic (classic)|Visual Basic 6.0]] (VB6) and used throughout the Microsoft Office programs such as [[Microsoft Excel|Excel]], [[Microsoft Word|Word]], [[Microsoft Outlook|Outlook]] and [[Microsoft PowerPoint|PowerPoint]]. Most VB6 code, including the use of Windows [[API]] calls, can be used in VBA. [[Power users]] and developers can extend basic [[end-user]] solutions to a professional solution with advanced automation, [[data validation]], [[Exception handling|error trapping]], and multi-user support.

The number of simultaneous users that can be supported depends on the amount of data, the [[task (project management)|task]]s being performed, level of use, and [[Software design|application design]]. Generally accepted limits are solutions with 1 GB or less of data (Access supports up to 2 GB) and it performs quite well with 100 or fewer simultaneous connections (255 concurrent users are supported).<ref>{{Cite web|title=Migrate an Access database to SQL Server|url=https://support.microsoft.com/en-us/office/migrate-an-access-database-to-sql-server-7bac0438-498a-4f53-b17b-cc22fc42c979|access-date=October 15, 2021|website=support.microsoft.com}}</ref> This capability is often a good fit for department solutions. If using an Access database solution in a multi-user scenario, the application should be "split". This means that the tables are in one file called the [[Front and back ends|back end]] (typically stored on a shared network folder) and the application components (forms, reports, queries, code, macros, linked tables) are in another file called the [[Front and back ends|front end]]. The linked tables in the front end point to the back end file. Each user of the Access application would then receive his or her own copy of the front end file.

Applications that run complex queries or analysis across large datasets would naturally require greater [[bandwidth (computing)|bandwidth]] and [[memory (computers)|memory]]. Microsoft Access is designed to [[wikt:scale|scale]] to support more data and users by linking to multiple Access databases or using a [[back-end database]] like Microsoft SQL Server. With the latter design, the amount of data and users can scale to enterprise-level solutions.

Microsoft Access's role in [[web development]] prior to version 2010 is limited. [[User interface]] features of Access, such as forms and reports, only work in [[Microsoft Windows|Windows]]. In versions 2000 through 2003 an Access object type called Data Access Pages created publishable web pages. Data Access Pages are no longer supported. The [[Jet Database Engine]], core to Access, can be accessed through technologies such as [[ODBC]] or [[OLE DB]]. The data (i.e., tables and queries) can be accessed by [[Web application|web-based applications]] developed in [[ASP.NET]], [[PHP]], or [[Java (software platform)|Java]]. With the use of Microsoft's [[Terminal Services]] and Remote Desktop Application in Windows Server 2008 R2, organizations can host Access applications so they can be run over the web.<ref>{{cite web|url=http://www.fmsinc.com/microsoftaccess/terminal-services/remoteapp.htm|title=Using Terminal Services and RemoteApp to Extend Your Microsoft Access and other Windows Applications Over the Internet|access-date=March 13, 2016}}</ref> This technique does not scale the way a web application would but is appropriate for a limited number of users depending on the configuration of the host.

Access 2010 allows databases to be published to [[Microsoft SharePoint Server|SharePoint]] 2010 web sites running Access Services. These web-based forms and reports run in any modern web browser. The resulting web forms and reports, when accessed via a web browser, do not require any add-ins or extensions (e.g., ActiveX and [[Silverlight]]).

Access 2013 can create web applications directly in [[Microsoft SharePoint Server|SharePoint]] 2013 sites running Access Services. Access 2013 web solutions store its data in an underlying SQL Server database which is much more scalable and robust than the Access 2010 version which used SharePoint lists to store its data.

Access Services in SharePoint has since been retired.<ref name="AccessServicesSharepointRetired">{{cite web|title=Access Services in SharePoint Roadmap|url=https://support.office.com/en-us/article/access-services-in-sharepoint-roadmap-497fd86b-e982-43c4-8318-81e6d3e711e8|publisher=Microsoft|access-date=May 20, 2019}}</ref>

A compiled version of an Access database (file extensions .MDE /ACCDE or .ADE; ACCDE only works with Access 2007 or later) can be created to prevent users from accessing the design surfaces to modify module code, forms, and reports. An MDE or ADE file is a Microsoft Access database file with all modules compiled and all editable source code removed. Both the .MDE and .ADE versions of an Access database are used when end-user modifications are not allowed or when the application's source code should be kept confidential.

Microsoft also offers developer extensions for download to help distribute Access 2007 applications, create database templates, and integrate [[source code]] control with [[Microsoft Visual SourceSafe]].