Microsoft Access is a database management system (DBMS) from Microsoft that combines Relational Microsoft Jet Database Engine with graphical user interface and software development tools. It is a member of a Microsoft Office application, included in the Professional and higher editions or sold separately.
Microsoft Access stores data in its own format based on the Access Jet Database Engine. It can also import or link directly to data stored in applications and other databases.
Software developers, data architects, and power users can use Microsoft Access to develop application software. Like other Microsoft Office applications, Access is supported by Visual Basic for Applications (VBA), an object-based programming language that can refer to various objects including DAO (Data Access Objects), ActiveX Data Objects, and many other ActiveX components. Visual objects used in forms and reports expose their methods and properties in the VBA programming environment, and the VBA code module can declare and invoke Windows operating system operations.
Video Microsoft Access
Histori
Project Omega
Microsoft's first attempt to sell relational database products was during the mid-1980s, when Microsoft acquired a license to sell R: Base. In the late 1980s Microsoft developed its own solution codenamed Omega. It was confirmed in 1988 that database products for Windows and OS/2 are under development. It will include the "Embedded Basic" EB language, which will be the language for writing macros in all Microsoft applications, but macro language unification does not occur until the introduction of Visual Basic for Applications (VBA). Omega is also expected to provide a front end to Microsoft SQL Server. This app is very source-hungry, and there are reports that it's working slowly on 386 processors available at the time. It was scheduled to be released in the 1st quarter of 1990, but in 1989 the product development was rearranged and scheduled to be submitted no sooner than in January 1991. Part of the project was later used for other Microsoft projects: Cirrus (code name for Access) and Thunder (code name for Visual Basic, where Embedded Basic engine is used). Following the premiere of Access, the Omega project was shown in 1992 to several journalists and included features not available in Access.
Project Cirrus
After the Omega project was canceled, some of its developers were assigned to the Cirrus project (mostly assigned to the team that created Visual Basic). The goal is to create a competitor for applications like Paradox or dBase that will work on Windows. After Microsoft acquired FoxPro, there were rumors that Microsoft's project might be replaced by it, but the company decided to expand it in parallel. It is assumed that the project will use Extensible Storage Engine (Jet Blue) but, in the end, only support for Microsoft Jet Database Engine (Jet Red) is provided. This project uses some code from both the Omega project and the pre-release Visual Basic version. In July 1992, a beta from Cirrus was sent to the developer and the name Access became the official name of the product.
Timeline
1992: Microsoft released Access version 1.0 on November 13, 1992, and released Access 1.1 in May 1993 to improve compatibility with other Microsoft products and to include the Access Basic programming language.
1994: Microsoft establishes minimum hardware requirements for Access v2.0 such as: Microsoft Windows v3.1 with 4 MB of RAM required, 6 MB RAM is recommended; It takes 8 MB of hard disk space, 14 MB of recommended hard disk space. Items are shipped on seven floppy disks of 1.44 MB. This guide shows the date of copyright 1994.
With Office 95, Microsoft Access 7.0 (a.k.a. "Access 95") becomes part of Microsoft Office Professional Suite, joins Microsoft Excel, Word, and PowerPoint and transitions from Access Basic to VBA. Since then, Microsoft has released a new version of Microsoft Access with every Microsoft Office release. These include Access 97 (version 8.0), Access 2000 (version 9.0), Access 2002 (version 10.0), Access 2003 (version 11.5), Access 2007 (version 12.0), Access 2010 (version 14.0), and Access 2013 (version 15.0 ).
Versions 3.0 and 3.5 of the Microsoft Jet database engine (used by Access 7.0 and Access 97 released later) have important issues that make this Access version unusable on computers with more than 1 GB of memory. While Microsoft fixes this issue for Jet 3.5/Access 97 after its release, it never fixes the issue with Jet 3.0/Access 95.
The original Access database format (MDB Jet Database) has also evolved over the years. The formats include Access 1.0, 1.1, 2.0, 7.0, 97, 2000, 2002, and 2007. The most significant switches are from Access 97 to Access 2000 format; which is not compatible with previous Access versions. Starting in 2011, all newer Access versions support the Access 2000 format. New features are added to the Access 2002 format that Access 2002, 2003, 2007, and 2010 can access.
Microsoft Access 2000 increases the maximum database size to 2GB from 1GB in Access 97.
Microsoft Access 2007 introduces a new database format: ACCDB. Supports links to SharePoint lists and complex data types such as multivalue fields and attachments. This new field type is basically a record in the field and allows the storage of multiple values ​​or files in one field. Microsoft Access 2007 also introduces the Attachment File field, which stores data more efficiently than the OLE (Object Linking and Embedding) field.
Microsoft Access 2010 introduces a new version of ACCDB format that is supported hosting Access Web solutions on SharePoint 2010 servers. For the first time, this allows the Access solution to run without having to install Access on their PC and is the first support of Mac users. Any user on a SharePoint site with sufficient privileges can use the Web Access solution. A copy of Access is still needed for the developer to create an Access Web solution, and the Access desktop version remains part of Access 2010. Web Access solutions are not the same as desktop solutions. Automation is only through a macro language (not VBA) that Access is automatically converted to JavaScript. The data is no longer in the Access database but the SharePoint list. Access desktop databases can be linked to SharePoint data, so hybrid apps are possible so that SharePoint users who need basic viewing and editing can be supported while more sophisticated traditional solutions can remain in the desktop Access database.
Microsoft Access 2013 offers traditional Access desktop solutions plus updated SharePoint 2013 web solutions. The Access Web model in Access 2010 is replaced by a new architecture that stores its data in the actual SQL Server database. Unlike the SharePoint list, it offers a true relational database design with referential integrity, scalability, extensibility and performance expected from SQL Server. Database solutions that can be created in SharePoint 2013 offer a modern user interface designed to showcase the different levels of relationships that can be viewed and edited, along with resizing for various devices and support for touch. Access 2013 desktop is similar to Access 2010 but some features are discontinued including support for Access Data Projects (ADPs), pivot tables, pivot charts, Access data collection, source code control, replication, and other legacy features. Access the maximum size of a 2GB fixed desktop database (as it has been since version 2000).
Prior to the introduction of Access, Borland (with Paradox and dBase) and Fox (with FoxPro) dominated the desktop database market. Microsoft Access is the first mass-market database program for Windows. With the purchase of FoxPro by Microsoft in 1992 and the incorporation of Fox's Rushmore optimization routines into Access, Microsoft Access quickly became the dominant database for Windows - effectively eliminating the competition that failed to transition from the MS-DOS world.
Access first name code is Cirrus; the form machine is called Ruby. This is before Visual Basic. Bill Gates looked at the prototype and decided that the BASIC language component should be developed together as a separate expandable application, a project called Thunder. Both projects are developed separately.
Access is also the name of a communication program from Microsoft, which is intended to compete with ProComm and other programs. This proves to be failed and dropped. Years later, Microsoft reused the name for its database software.
Maps Microsoft Access
Usage
In addition to using their own database storage files, Microsoft Access can also be used as a 'front-end' of a program while other products act as 'back-end' tables, such as Microsoft SQL Server and non-Microsoft products such as Oracle and Sybase. Some backend sources can be used by 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 tables and queries. Microsoft Access can 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 controls.
Access tables support a variety of standard fields, indexes, and referential integrity including cascading updates and deletions. Access also includes a query interface, a form to display and enter data, and reports to print. The underlying Jet database, which contains these objects, is multi-user and handles record-locking.
Repetitive tasks can be automated via macros with a point-and-click option. It's also easy to put the database on the network and have multiple users share and update the data without overwriting their respective jobs. Data is locked at a very different note level than Excel that locks the entire spreadsheet.
There are database templates in the program and to be downloaded from the Microsoft website. This option is available when starting Access and allows users to upgrade the database with specified tables, queries, forms, reports, and macros. The database template supports VBA code but the Microsoft template does not include VBA code.
Programmers can create solutions using VBA, which is similar to Visual Basic 6.0 (VB6) and is used throughout Microsoft Office programs like Excel, Word, Outlook, and PowerPoint. Most VB6 code, including use of Windows API calls, can be used in VBA. Users and power developers can extend basic end-user solutions to professional solutions with advanced automation, data validation, error traps, and multi-user support.
The number of simultaneous users that can be supported depends on the amount of data, tasks performed, usage levels, and app design. The commonly accepted limit is a solution with 1 GB or less of data (Access supports up to 2 GB) and it works reasonably well with 100 or fewer simultaneous connections (255 concurrent users supported). This ability is often suitable for departmental solutions. If using an Access database solution in a multi-user scenario, the application must be "shared". This means that the table is in a single file called the back (usually stored in a shared network folder) and the application component (form, report, query, code, macro, linked table) is in another file called the front end. Tables are connected at the front end point to the back end file. Each user of the Access application will then receive a copy of itself from the front end file.
Applications running queries or complex analysis in large datasets will naturally require greater bandwidth and memory. Microsoft Access is designed to scale to support more data and users by connecting to multiple Access databases or using back-end databases such as Microsoft SQL Server. With the latest design, the amount of data and users can be upgraded to enterprise-level solutions.
The role of Microsoft Access in web development before the 2010 version is limited. Access user interface features, such as forms and reports, work only on Windows. In versions 2000 to 2003 an access object type called Data Access Pages creates a web page that can be published. The Data Access page is no longer supported. Microsoft Jet Database Engine, core to Access, can be accessed through technologies such as ODBC or OLE DB. Data (i.e., tables and queries) can be accessed by web-based applications developed in ASP.NET, PHP, or Java. By using Microsoft Terminal Services and Remote Desktop Applications in Windows Server 2008 R2, organizations can host Access applications so they can be run over the web. This technique does not measure the way the web app is but is appropriate for a limited number of users depending on the host configuration.
Access 2010 enables the database to be published to SharePoint 2010 websites running Access Services. These web based forms and reports run on any modern web browser. The generated web forms and reports, when accessed via a web browser, require no additional or extension (e.g., ActiveX, Silverlight).
Access 2013 can create web applications directly on SharePoint 2013 sites running Access Services. Access 2013 web solution stores its data in its underlying SQL Server database that is much more scalable and robust than the version of Access 2010 that uses SharePoint lists to store its data.
The compiled version of the Access database (File extension:.MDE/ACCDE or.ADE; ACCDE only works with Access 2007 or later) can be created to prevent users from accessing the design surface 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 deleted. Both versions of.MDE and.ADE from the Access database are used when end user modification is not allowed or when the application source code must be kept private.
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.
Features
Users can create tables, queries, forms, and reports, and link them to macros. Advanced users can use VBA to write rich solutions with advanced data manipulation and user control. Access also has a report generation feature that can work with any Access data source.
The original concept of Access is for end users to access data from any source. Other features include: import and export data to many formats including Excel, Outlook, ASCII, dBase, Paradox, FoxPro, SQL Server, and Oracle. It also has the ability to connect to data in an existing location and use it for viewing, querying, editing, and reporting. This allows existing data to change while ensuring that Access uses the most recent data. It can perform a heterogeneous union between data sets stored on multiple platforms. Access is often used by people who download data from enterprise-level databases for manipulation, analysis and reporting locally.
There is also a Jet Database format (MDB or ACCDB in Access 2007) that can contain applications and data in a single file. This makes it very easy to distribute the entire app to other users, who can run it in an unrelated environment.
One of the benefits of Access from a programmer's perspective is its relative compatibility with SQL (structured query language) - queries can be viewed graphically or edited as SQL statements, and SQL statements can be used directly in Macros and VBA Modules to manipulate Access tables. Users can mix and use VBA and "Macro" for form and programming logic and offer object-oriented possibilities. VBA can also be included in the request.
Microsoft Access offers parameter questions. These access questions and tables can be referenced from other programs such as VB6 and.NET via DAO or ADO. From Microsoft Access, VBA can reference parameter storage procedures via ADO.
The Microsoft SQL Server desktop edition can be used with Access as an alternative to the Jet Database Engine. This support begins with MSDE (Microsoft SQL Server Desktop Engine), a reduced version of Microsoft SQL Server 2000, and continues with SQL Server Express versions of SQL Server 2005 and 2008.
Microsoft Access is a file-based database server. Unlike relational client-server (RDBMS) database management systems, Microsoft Access does not implement database triggers, stored procedures, or transaction logging. Access 2010 includes table-level triggers and stored procedures built into the ACE data engine. Thus, the Client-server database system is not a requirement to use stored procedures or table triggers with Access 2010. Tables, queries, forms, reports, and macros can now be developed specifically for web-based applications in Access 2010. Integration with Microsoft SharePoint 2010 is also greatly improved.
2013 Microsoft Access Edition introduces the most flat design and the ability to install applications from the Office Store, but not introduce new features. This theme is partially updated for 2016, but no dark theme is created for Access.
Access Service and Web database
The ASP.NET web form can query the Microsoft Access database, take notes and display it in the browser.
SharePoint Server 2010 through Access Services makes it possible to access the 2010 database to be published to SharePoint, allowing multiple users to interact with database applications from standard Web browsers that match standards. Web database access published to a SharePoint Server can use standard objects such as tables, queries, forms, macros, and reports. The Access service stores these objects in SharePoint.
Access 2013 offers the ability to publish Access web solutions in SharePoint 2013. Instead of using SharePoint lists as their data source, Access 2013 uses a SQL Server database hosted by SharePoint or SQL Azure. It offers a true relational database with referential integrity, scalability, maintenance, and extensibility compared to the SharePoint Access 2010 view being used. Macro language is enhanced to support more advanced programming logic and database-level automation.
Import or link source
Microsoft Access may also import or link directly to data stored in apps and other databases. Microsoft Office Access 2007 and later can import from or link to:
- Microsoft Access
- Excel
- SharePoint List
- Plain text
- XML
- Outlook
- HTML
- dBase (down at Access 2013; restored in Access 2016)
- Paradox (with Access 2007; down at Access 2010)
- Lotus 1-2-3 (down in Access 2010)
- Container data compatible with ODBC, including:
- Microsoft SQL Server
- Oracle
- MySQL
- PostgreSQL
- IBM Lotus Notes
- AS 400 DB2
Microsoft Access Runtime
Microsoft offers a free runtime version of Microsoft Access that allows users to run an Access desktop application without the need to purchase or install a retail version of Microsoft Access. This allows Access developers to create databases that can be distributed freely to end users in unlimited quantities. Access 2007 and later versions runtime can be downloaded for free from Microsoft. The runtime version for Access 2003 and earlier was part of the Office Developer Extensions/Devices and required a separate purchase.
The runtime version allows users to view, edit, and delete data, along with running queries, forms, reports, macros, and VBA module code. The runtime version does not allow users to change Microsoft Access table designs, queries, forms, reports, macros or module codes. The runtime version is similar to the full complete version of Access and is usually compatible with previous versions; for example Access Runtime 2010 allows users to run Access applications created with versions of 2010 as well as 2007 to 2000. Due to the features left in Access 2013, the runtime version also can not support the old features. During development one can simulate a runtime environment from a fully functional version by using the command line option /runtime .
Development
Access stores all database tables, queries, forms, reports, macros, and modules in the Access Jet database as a single file.
For query development, Access offers "Query Designer", a graphical user interface that allows users to create queries without a structured query language knowledge. In Query Designer, users can "show" query data sources (which can be tables or queries) and select the fields they want to return by clicking and dragging them into the grid. One can set up join by clicking and dragging fields in the table to a field in another table. Access allows users to view and manipulate SQL code if desired. Any Access table, including linked tables from different data sources, can be used in queries.
Access also supports creating "pass-through queries". This SQL code snippet can resolve external data sources through the use of ODBC connections on the local computer. This allows the user to interact with data stored outside the Access program without using a linked table or Jet. Users build pass-through queries using SQL syntax supported by external data sources.
When developing a report (in "Design View") the addition or change to the control causes any related query to run in the background and the designer is forced to wait for the recording to be returned before it can make another change. This feature can not be turned off.
Non-programmers can use the macro feature to automate simple tasks through a series of drop down options. Macros allow users to easily manage shared commands such as running queries, importing or exporting data, opening and closing forms, previewing and printing reports, etc. Macros support basic logic (IF-conditions) and the ability to call other macros. Macros can also contain sub-macros similar to subroutines. In Access 2007, enhanced macros include error handling and support for temporary variables. Access 2007 also introduces embedded macros that are basically the properties of an object event. This eliminates the need to store macros as individual objects. However, the macro is limited in functionality with the lack of programming loops and advanced coding logic up to Access 2013. With significant further improvements introduced in Access 2013, the macro capabilities become fully comparable with VBA. They create dependable rich web-based application deployment features, through highly refined Microsoft SharePoint interface and tools, as well as on traditional Windows desktops.
Similar to other products in the Microsoft Office suite, another programming language used in Access is Microsoft VBA. It's similar to Visual Basic 6.0 (VB6) and the code can be stored in the modules, classes, and code behind forms and reports. To create a richer, more efficient and more sustainable finished product with good error handling, most professional Access applications are developed using VBA programming languages ​​rather than macros, except where web deployment is a business requirement.
To manipulate data in tables and queries in VBA or macro, Microsoft provides two COM component data access libraries:
- Data Access Objects (DAO) (only 32-bit), which are included in Access and Windows and evolved into ACE in Microsoft Access 2007 for ACCDE database format
- ActiveX Data Objects ActiveX Objects (ADO) (32-bit and 64-bit versions)
In addition to DAO and ADO, developers can also use OLE DB and ODBC to develop original C/C programs for Access. For ADP and direct manipulation of SQL Server data, ADO is required. DAO is most appropriate for managing data in Access/Jet databases, and the only way to manipulate complex field types in the ACCDB table.
In the database container or navigation pane in Access 2007 and later versions, the system automatically categorizes each object by type (for example, tables, queries, macros). Many Access developers use the Leszynski naming convention, though this is not universal; it is a programming convention, not a rule that DBMS implements. This is helpful in VBA where a reference to an object name may not indicate its data type (eg tbl for tables, qry for queries).
Developers deploy Microsoft Access most frequently for individual projects and workgroups (Access 97 speed characterization is performed for 32 users). Since Access 97, and with Access 2003 and 2007, Microsoft Access and hardware have evolved significantly. The database is under 1 GB in size (which can now be fully installed in RAM) and 200 simultaneous users are in Microsoft Access capabilities. Of course, performance depends on the design and task of the database. Intensive-disk work such as complex search and search takes the longest time.
Because data from a Microsoft Access database can be cached in RAM, processing speed can be greatly increased when there is only one user or if the data does not change. In the past, the packet latency effects on the record-locking system caused the Access database to run slowly on a virtual private network (VPN) or wide area network (WAN) against the Jet database. In 2010 broadband connections have reduced this problem. Performance can also be improved if continuous connections are maintained to the back-end database throughout the session rather than opening and closing them for each table access. If Access database performance via VPN or WAN suffers, then clients using Remote Desktop Protocol (such as Microsoft Terminal Services) can provide effective solutions. Access databases that connect to SQL Server or to Access Data Projects work well through VPN and WAN.
In July 2011, Microsoft acknowledged intermittent performance issues with all versions of Access and Windows 7 and Windows Server 2008 R2 due to the very different resource management properties in newer operating systems. This issue greatly affects query performance in Access 2003 and earlier with Jet Database Engine code, as well as Access 2007 and later with Access Database Engine (ACE). Microsoft has issued a KB2553029 hotfix for Access 2007 and KB2553116 for Access 2010, but will not fix the problem with Jet 4.0 as there is no mainstream support.
In earlier versions of Microsoft Access, the ability to distribute apps required the purchase of the Developer Toolkit; in Access 2007, 2010 and Access 2013, the "Runtime Only" version is offered as a free download, making royalty-free app distributions possible on Windows XP, Vista, 7 and Windows 8.x.
Divide database architecture
Microsoft Access applications can adopt split-database architecture. A single database can be divided into separate "back-end" files containing data tables (shared on the file server) and "front-end" (containing application objects such as questions, forms, reports, macros, and modules). The "front-end" Access app is distributed to each user's desktop and linked to a shared database. Using this approach, each user has a copy of Microsoft Access (or runtime version) installed on their machine along with their application database. This reduces network traffic because the app is not taken for every use. The "front-end" database can still contain local tables to store user settings or temporary data. The split-database design also allows independent application development of data. One disadvantage is that users can make various changes to their own local copy of the application and this makes it difficult to manage version control. When the new version is ready, the front-end database is replaced without affecting the database data. Microsoft Access has two built-in utilities, Database Splitter and Linked Table Manager, to facilitate this architecture.
Tables linked in Access use absolute paths rather than relative paths, so the development environment must have the same path as the production environment or the dynamic-linker routine can be written in VBA.
For a very large Access database, this may have performance issues and SQL backend should be considered in these circumstances. This is less of a problem if the entire database can go into PC RAM because Access stores data and indexes.
Migrate to SQL Server
To scale an Access application to a company or web solution, one technique might involve migrating to a Microsoft SQL Server or equivalent database server. The client-server design significantly reduces maintenance and improves security, availability, stability, and transaction recording.
Access 2010 includes a feature called Upsizing Wizard that allows users to upgrade their databases to Microsoft SQL Server, the ODBC client-server database. This feature is removed from Access 2013. Additional solutions, SQL Server Migration Assistant for Access (SSMA), continue to be available for free download from Microsoft.
Various upgrade options available. After migrating data and queries to SQL Server, the Access database can be linked to the SQL database. However, certain types of data are problematic, especially "Yes/No". In Microsoft Access there are three statuses for data types Yes/No (True/False): empty, no/false (zero) and yes/true (-1). The appropriate SQL Server data type is binary, with only two states, allowed values, zero and 1. Regardless, SQL Server is still the easiest migration, and most appropriate especially if the user does not have the right to create objects such as stored procedures in SQL Server. Taking data from linked tables is optimized only to the required records, but this scenario may operate less efficiently than it should be optimal for SQL Server. For example, in the case where multi-table joins still require copying entire tables across the network.
In previous Access versions, including Access 2010, databases can also be converted to Access Data Projects (ADP) that are tied directly to one SQL Server database. This feature is removed from Access 2013. ADP support the ability to directly create and modify SQL Server objects such as tables, views, stored procedures, and SQL Server constraints. View and stored procedures can significantly reduce network traffic for multi-table combined. Fortunately, SQL Server supports temporary tables and links to other data sources outside of a single SQL Server database.
Finally, some Access databases are completely replaced by other technologies such as ASP.NET or Java after data is converted. But any migration can dictate great effort because the Access SQL language is a more powerful superset than standard SQL. Furthermore, the Access application procedure, whether VBA and macro, is written at a relatively higher level compared to the currently available strong and comprehensive alternatives. Note that the Access macro language, allowing a higher level of abstraction than VBA, is significantly improved in Access 2010 and again in Access 2013.
In many cases, developers build a direct web-to-data interface using ASP.NET, while maintaining a major business automation process, unnecessary administrative and reporting functions are distributed to everyone in Access for maintenance by information workers.
While all data access can migrate to SQL Server directly, some questions can not migrate successfully. In some situations, you may need to translate VBA functions and user-defined functions to a T-SQL or.NET function or procedure. Query crosstab can migrate to SQL Server using PIVOT command.
Protection
The Microsoft Access application can be created securely with various methods, the most basic of which is password access control; this is a relatively weak form of protection.
A higher level of protection is the use of workgroup security that requires a username and password. Users and groups can be specified along with their rights in the object type or the level of individual objects. This can be used to specify a person with read-only rights or data entry but may be challenging to specify. A separate workgroup security file contains settings that can be used to manage multiple databases. Workgroup security is not supported in the Access 2007 and Access 2010 ACCDB database formats, although Access 2007 and Access 2010 still support it for the MDB database.
The database can also be encrypted. The ACCDB format offers much more advanced encryption than previous versions.
In addition, if the database design must be secured to prevent changes, Access databases can be locked/protected (and compiled source code) by converting the database into.MDE files. All changes to the VBA project (modules, forms, or reports) must be created to the original MDB and then converted back to MDE. In Access 2007 and Access 2010, the ACCDB database is converted to an ACCDE file. Some tools are available to unlock and "decompile", although some elements including original VBA comments and formatting are usually not fixed.
File extension
Microsoft Access stores information under the following file formats:
Version
There is no Access version between 2.0 and 7.0 because the version of Office 95 is launched with Word 7. All Office 95 products have OLE 2 capability, and Access 7 indicates that it is compatible with Word 7.
Version number 13 is bypassed.
See also
- Comparison of relational database management system
- Forms (web)
- MDB Tools
- Kexi
References
This article is based on material extracted from the Free Online Computing Dictionary before November 1, 2008 and is incorporated in the "subscription" provision of GFDL, version 1.3 or later.
External links
- Official website
- Access Blog
- Microsoft Access Update Version, Service Pack, Hotfix, and Update History
Source of the article : Wikipedia
0 Comments