Oracle_vs_MicrosoftAccess_paper.pdf_____

Sharif S. & Christopher S. 1
Oracle Apex V.S. Microsoft Access
Sharif S. & Christopher S.
California State University, Los Angeles
CIS 4580 – E-Business Applications Development With Oracle
Professor Khoee
December 8th
2024

As databases lead the technology industry, a key question arises: which
DBMS should we choose? With so many options available, which one stands out?
In this paper, we will explore two of the most recognized databases in the tech
world—Oracle APEX and Microsoft Access. We will cover the historical timelines
of both DBMSs and examine their differences and similarities, ranging from
security features to user-friendliness. Additionally, we will discuss the main
functionalities of each DBMS.
Let’s dive into Microsoft Access Database Management System. The first
version, Microsoft Access 1.0, was released in 1992, introducing a user-friendly
interface designed to simplify database creation and management for individuals
and small businesses. What set it apart from other database management systems
was its ability to allow users to create complex tables, forms, and reports through
selection and drag-and-drop functionality, all without needing to write code—truly
groundbreaking at the time. Being part of Microsoft company, it also incorporated
features familiar from Microsoft Office, such as the ribbon interface, which would
influence future versions.
A significant update occurred in 1995, when Microsoft Access was
integrated into the Microsoft Office suite, bringing it in line with other widely used
applications like Word, Excel, and PowerPoint. This integration proved beneficial

for Microsoft, as the net income surged to $1.453 billion that year—perhaps due to
Access finally joining the Office family. This marked an important moment in
Microsoft's history.
As we entered the 2000s, Microsoft Access underwent substantial changes,
including significant performance improvements and increased database size
limits. The year 2000 also introduced data access pages, enabling users to create
web-based database interfaces. This version enhanced usability by offering
features like a user-friendly interface, customizable templates, a powerful query
designer, integrated reporting tools, customizable forms, macros for automation,
and the ability to establish complex relationships between tables.
In the 2007 version, Microsoft Access embraced the now-famous Microsoft
Office Fluent ribbon interface, optimizing user interaction. This update also
introduced a new database format, .accdb, enabling SharePoint list support. The
2007 release gained significant traction, leading to further enhancements and
consistent updates in the 2016 and 2019 versions, which improved Microsoft
Access continuously.
Now, let’s discuss the differences and similarities between Microsoft Access
and Oracle APEX. While both platforms have unique features, a significant
difference is that Microsoft Access operates solely on local desktops. This can be
seen as a double-edged sword in today's remote work environment, where

accessibility from anywhere is essential—something Oracle APEX excels at since
it operates as a cloud-based service. In contrast, Microsoft Access is a software
application that must be downloaded on Windows devices, leaving Mac users
without access to its features.
Another unique aspect of Microsoft Access is its well-known ribbon
interface, familiar to many users as it hosts formatting and layout tools. This user-
friendly design is a notable advantage that Oracle APEX lacks. Brand recognition
is vital in tech, and Microsoft’s reputation makes Access an easily learnable option
for many. Microsoft Access also features an intuitive auto-relationship wizard,
helping users determine the relational cardinality between tables, automating some
of the database setup work.
Additionally, Microsoft Access supports SQL through query layering,
allowing users to extract or create data. Both Microsoft Access and Oracle APEX
are relational database management systems (DBMS), meaning they organize data
into structured tables comprising rows and columns. Each table relates to a specific
entity, with rows representing individual records and columns defining the
attributes of the data. The “relational” aspect comes from how these tables are
interconnected through keys, with primary keys uniquely identifying records and
foreign keys linking tables together. These relationships can be one-to-one, one-to-
many, or many-to-many, depending on the data's structure. Relational databases

emphasize data integrity and reduce redundancy through normalization, ensuring
consistency and efficiency. Users can seamlessly retrieve, update, and manipulate
data using Structured Query Language (SQL).
For instance, in a bookstore database, a Books table with book details, a
Customers table with customer information, and an Orders table tracking purchases
can be interconnected through foreign keys like CustomerID and BookID. This
interconnected design facilitates flexible and scalable data management, making
relational databases fundamental to modern technology and information systems.
Furthermore, data-centric databases prioritize the data itself, making it the
focal point rather than merely supporting specific applications or systems. This
method allows for centralized data management, storage, and organization,
ensuring easy access across various platforms while maintaining consistency and
preventing data duplication. Centralized storage simplifies scaling as data volume
increases and streamlines integration with other systems. Data-centric databases
also include features for security, accuracy, and regulatory compliance. They
facilitate analytics, allowing businesses to leverage their data for informed
decision-making. For example, a company might utilize a data-centric database to
consolidate customer information, sales data, and inventory in one location,
enabling marketing, sales, and supply chain teams to draw from a common source,

thereby enhancing efficiency and reducing the likelihood of errors. The goal is to
keep operations organized, efficient, and prepared for future developments.
Oracle APEX embraces the concept of centralized databases accessible
globally via the cloud. In contrast, Microsoft Access has not adopted this cloud-
based approach that many tech companies are pursuing. Microsoft Office can only
be used locally on one’s device. It's peculiar that this software is restricted to
specific machines, particularly Microsoft PCs. Not only is it unavailable on other
operating systems like macOS, but it also lacks cloud capabilities, hindering
effortless collaboration with other users. A crucial aspect of the tech industry is the
ability to collaborate freely with users worldwide, and Microsoft Access's
limitation to localized use is cumbersome. Users must have the specific machine
available, which can be quite inconvenient. Moreover, Microsoft Access imposes a
maximum file size limit of 2GB, restricting high-scale, high-volume projects and
compelling users to store files on their local computer systems instead.Storage is
specifically filled in a single file format also known as .accdb or.mdb that
encapsulates everything of the table from its queries forms and even reports if the
user wanted to.
Now, let's explore the core functionalities of Microsoft Access, which
essentially highlight the software's value and answer the question of why to use it.
This section will discuss the key features of the system, focusing on the ability to

create and share applications with optimal compatibility within the Microsoft suite,
all without requiring any coding expertise. The accessibility of this software
demonstrates its ease of use, allowing any user to jump in and navigate without
prior knowledge. Understanding the user-friendliness of Microsoft Access is
crucial, especially when compared to Oracle APEX, where familiarity with the
system is essential for effective navigation SQL. When considering the differences
between Microsoft Access SQL and Oracle APEX SQL, it can be helpful to
imagine how each might be used in a university setting, such as at Cal State LA.
Suppose a small group of professors keeps a local database in Access to track
students, classes, and assignments for a few courses. The SQL queries they run—
such as listing students enrolled in a given class or calculating the average grade—
are simple, performed directly on a file-based database, and easily managed with
minimal technical overhead. This approach is convenient for a limited number of
users and moderate amounts of data.
In contrast, consider the larger, institution-wide needs of Cal State LA’s
administration. For example, when an entire college department wants to analyze
multiple semesters’ worth of class enrollments, professor workloads, and student
performance across various programs, the more robust capabilities of Oracle
APEX become essential. Here, the SQL interacts with a powerful Oracle Database
that supports complex queries, intricate data relationships, and high-volume

transactions. Professors and staff can rely on APEX applications to produce
detailed reports—such as tracking the progress of students in different classes over
time or measuring the impact of newly introduced courses on graduation rates.
Oracle SQL and PL/SQL functions, triggers, and stored procedures enhance this
environment, enabling a richer set of features and scalability that a large, data-
driven institution needs.
Next, we will discuss the security aspect of our paper. Databases often
contain sensitive user information, making it essential for their security measures
to be robust enough to prevent any incidents. Therefore, considering security in
each software is crucial, and in this case, Microsoft Access does not offer the
strongest security features, much like other software in the Microsoft suite. For
example, when you sign into Microsoft Word, it seems like there is an open access
to all data, indicating a lack of security layers for such software. This is
particularly significant for Microsoft Access, as it holds sensitive user data,
including personal identifiable information. Unfortunately, the security primarily
consists of a basic passcode to access the database, which is inadequate.
Additionally, it does not include sufficient user authentication or advanced
encryption protocols. Moreover, it separates database security from backend
networks, enabling limited data sharing. In reality, there isn’t a user-level security
mechanism in place. Ultimately, if you wish to bolster the security of your

database file, the only option is to set a password. Unlike Oracle Apex, for
example, where security is a primary focus, Microsoft Access lacks advanced
encryption features.
Another important question is how each platform facilitates data integration
and connectivity with other systems. Microsoft Access simplifies this process by
utilizing Open Database Connectivity (ODBC) data sources, allowing users to link
to external data even when built-in drivers aren’t available. It also supports a type
of business connectivity integration in a read-only format. For example, importing
a BCM file can establish a static link to external data stored within an Access
database on a local machine. While the data remains read-only, it can still be
periodically refreshed, providing users with updated information without complex
setup.
In contrast, Oracle APEX operates within the Oracle Database ecosystem
and consequently offers more robust and dynamic integration capabilities. Rather
than relying solely on file-based connections, APEX can leverage features such as
database links, RESTful Web Services, and Oracle REST Data Services (ORDS)
for real-time interactions with external systems. At an institution like Cal State LA,
this means that professors and administrators could integrate APEX applications
with various campus databases, learning management systems, or student
information systems, ensuring that class rosters, enrollment details, and

performance metrics are consistently up-to-date. By facilitating seamless, two-way
communication, APEX helps eliminate data silos and streamline workflows,
ultimately supporting more informed decision-making and efficient operations at
an enterprise scale.
The final topic we’ll discuss is Microsoft Access pricing, highlighting that
nothing in life is truly free. Even free trials often require something in return for
the software. Unlike Oracle APEX, Microsoft Access does not offer a free trial or
version. It can be purchased outright, or included in a bundle with other Microsoft
software, with pricing options for personal or business use, as well as subscription
plans billed monthly or annually. While most of us are familiar with Microsoft's
user interface, it's important to note there’s no free version available for crucial
software tools. This reflects the ongoing trade-off in today’s tech landscape:
despite being at the forefront of innovation, there will always be costs involved.
The key question is how reliable this database system is—will it be essential for
everyone or something that can be overlooked? There is a plethora of free software
available; so why not consider that instead of Microsoft, which may not be optimal
for larger companies or extensive datasets? This positions Oracle APEX as a
stronger option in terms of affordability and scalability, as it is designed for
smaller-scale operations, unlike Access.

APEX timeline
Now starting up years later is Oracle Apex created my one of the giants in
the Database management system scene. It was built as a low code solution for
users to be able to effectively build and modify applications without the need of in-
depth coding knowledge. According to Oracle themselves, “Oracle APEX is the
world’s most popular enterprise low-code application platform that enables you to
build scalable, secure web and mobile apps, with world-class features, that can be
deployed anywhere” so it is safe to say they are proud of their software.
Now low code, what is it? It does sound simple enough for someone who is
familiar with programming and other computer-related fields but not everyone in
an enterprise is. To explain it simply, low code refers to a method of building
software without the need to use a programming language such as Python, java, or
SQL. Instead, the building is done via dragging and dropping plus option selection
in forms. Imagine the difference between a command prompt versus the file system
on a personal computer!
Continuing with a timeline of Apex it started as HTML database way back
in the year 2004 as a web based development environment for developers to use
Structured Query Language to be able to build web applications based off of
databases and kept up integrity by managing the session state in order to allow
multiple users to update the application simultaneously. In 2006 there was a major

shakeup, and the application was renamed to Oracle Application Express but was
referred to as APEX for short. This was their major 2.0 release for consumers to
use. Now the following year they released the next major update thay came with
various features, including PDF Printing, Flash charting and Access Application
Migration. There would not be any major updates released until years later in
2009.That is not to say nothing changed over these years, in fact there was a pretty
large boost to low code users in 3.1 update that among other features, included a
feature known as interactive reporting which allowed all users to customize a
report without programmers doing the workload, using techniques such as filtering,
sorting, group-by, choosing displayed columns and others. This feature was a leap
forward for Application Express’s ease of use. The update also allowed users to
even save multiple versions of their customized reports. These people could now
let anyone conduct creation for their corporation. Of course, there were still limits
as programmers could limit which features are enabled by any individual to protect
the database. Following that in 2010 4.0 came out and brought with it changes too,
these changes allowed Dynamic Actions which allow reacting to changes on a
page without the developer having to write custom JavaScript for the application
being built. Another feature added was plugins that allowed web application
developers to create custom components such as items, regions and processes, that
can be reused across pages and applications. Finally, Oracle also added Web sheets

and RESTful Web for compatibilities with other services. And in the .1 and the
.1.1 updates added a WIKI and a new builder theme and other background
improvements. The 4.2 update in late 2012 added mobile device support that added
application builder on mobile devices as well as Hypertext Markup Language gen
5 support. After that there really were no major updates in the decimal updates,
they consisted mostly of bug fixes until 5.0 was released three years later. This was
the major of the major updates as it introduced many new features such as but not
limited to the page designer an innovation of low code development that allowed
users to drag and drop parts of the page and properties. It also introduces the
universal theme which granted users a responsive interface for applications which
can intuitively and with minimal hassle be customized using template options and
the theme roller. Over the next two years it remained as the default version with
some cumulative updates with bug fixes and other minor changes behind the
scenes and some new compatibility features with Oracle Java Extension Toolkit,
Quick SQL, REST Client Assistant, and Competitive Analysis.
That was the last update within the old version numbering system in 2018 to
fall in line with the rest of the Oracle suite of products the version convention was
to place the year that it released as the version number and the quarter that it
released as the sub marker. The only other updates in 2018 were for updating the
font, design details, and JavaScript API documentation. The “19th” version came

with many neat features such as a dark mode for users to use, new value types and
item types to go with an updated search engine and form components. Version 20
came with some continuations on the previous new faceted search engine and
allowed implementation of cascading list of values, conditional facets, and
compact count display. It also brought in collaboration with Oracle Redwood to
streamline the user experience to Oracle’s design system. 20.2 also gave users
access to the cards system and automation features and printing report systems. In
2021 Application Express brought in a map component in addition to support for
maps and calendars, and also major enhancements to REST Data Sources,
Reporting, Security, Universal Theme and Theme Roller. Plus, there was the
announcement of the GitHub repository to allow users to collaborate and
release/use starter or sample apps or plugins without relying on only oracle or what
the in-house developers can develop. Update 22 came with a rename to APEX as
that is how everyone had been referring to application express for years, this
release introduces several new features, including application search, API process
invocation, enhanced approvals, PWA improvements, geolocation support, a new
date picker, refreshable dynamic content regions, and CLOB session state. In
update 23 Apex brings exciting new features, including Application Working
Copies, Workflow, new page items like Combobox, Image Upload, and QR Code
Generator, customizable map backgrounds, support for Fusion Apps Extensions,

object storage for static resources. Finally, this year that we are in has had one
update that introduces a suite of AI-powered features, including generative AI
services, conversational AI dialogs, and the APEX_AI API. It also includes new
and updated components, such as select one and select many items, and faster,
more flexible template components. Additionally, it offers enhancements to
workflow, approvals, developer experience, user experience, and accessibility.
That update brings us up to date with the current version of Oracle Apex available
to consumers until next years model comes out, maybe in as little as three weeks!
Comparisons
Pricing
Pricing models for both Apex and Access differ on what they are priced as
important for their users to be charged. Access uses a per subscriber model where
more users included in a plan the rate will go down on a individual price but it still
goes up for the company being billed. You can also purchase a license to use
access as an induvial user at a price of 180 for a permanent license or you can get it
as a part of the Microsoft suite of programs where you can get it with Word,
PowerPoint, Excel, and more! And that suite is also available as a subscription
model where the buyer pays either a monthly subscription or an annual
subscription.

Contrary to Access, Oracle Apex does not have a user-based pricing model,
instead they sell their low-code development application with a pricing model
based on company needs. An enterprise can have as many users registered and
logged in at the same time as they want and it would not cost them a penny more,
besides employment and building costs. Now while Apex does have a free tier for
use it is restricted in the features that it offers for use. The free tier only grants
access to using APEX itself, the management system and all the developers, users,
and applications that the administrator wants, as well as direct database
connectivity and full instance cloning. Now to add more features that some
businesses do need there is a cost to it starting 102 dollars for the ability to use
elastic compute and store, Auto scale, Automatic backups and connectivity with
other databases such as azure and Oracle Cloud Interface (OCI). Finaly at the high
end starting at 502 dollars grants the ability to use all the previous features in
addition to auto failover to standby and the autonomous database.
Data management
Oracle is expected to be used via a browser and as such is not tied down to
be local on device for its storage. Instead, everything is stored on oracles servers
up on the cloud. This grants availability of users' data from anywhere they may be
as long as they have a device that has an internet connection. Thanks in large part

to oracles' cloud storing the data instead of it being stored on a device allows
means that the editing and updates can be done relatively quickly. That said if the
database administrator would be interested, they could keep the data stored locally
in order to keep it closer to home and under their control. Thanks to the could
being almost infinite, the only limit to the file size will be when oracle contacts
you to let you know its size on its cloud platform
Meanwhile Access has a different idea for keeping data stored, as it is an
application that is on devices. The database and the application that is being bult
gets stored locally on the device and all the tables, queries, forms, and reports are
stored in one file, either a .accdb file or .mdb file. This storage solution grants great
control over the data and keeps it safe, however it does not allow for multiple users
to update it dynamically which is definitely a demerit. Essentially your file size
will only be limited to the space that the device it is stored in is capped at.
Usage
Both Apex and Access have been excellent systems that allow users with
minimal to no coding knowledge to be able to build, modify and publish
applications that meet business needs. As mentioned above if you are familiar with
general Microsoft products such as Word, PowerPoint and Excel than you will
have an easy go with Access and its user interface similarities to the rest of the
suite such as the top bar ribbon and the similar control scheme. Meanwhile, Apex

is also quite friendly for beginners as it has all the options available once you log
in. The user would just read the buttons option on the display right in front of
them. While there is a section for adding and retrieving data to both systems using
Structured query language, it is not needed you can still build up whatever you
need, although using a coding language will bring more specific controls and
deeper understanding to the program. One of the biggest differences between the
two programs is the very powerful ribbon feature of Microsoft access that allows a
user to operate their database with ease and familiarity. And in addition to that is
the cross compatibility with other programs of Microsoft such as excel. That is not
to say there is not anything to boon within APEX as it has its compatibility with
oracle’s application suite such as Fusion cloud. In addition, there are also the many
apps and other APIs that are available to be used with a user built by both Oracle
corporate and the Oracle user community. to lay it down more Oracle APEX and
Microsoft Access are both powerful database tools, but they cater to different
needs. Oracle APEX is a robust, enterprise-grade low code platform for building
web applications, leveraging the power of Oracle Database. It's ideal for large-
scale, high-performance applications that require advanced security, scalability,
and integration with other enterprise systems. On the other hand, Microsoft Access
is a user-friendly tool for smaller-scale, departmental applications. It's well-suited

for simple data management tasks, form creation, and report generation, often used
by individuals or small teams with limited technical expertise.
Scalability
Oracle Apex and Access are both very popular solutions towards enterprises
looking towards making their own applications while not needing to have a large
scale of developers on hand and an overly complicated system that disallows entry
level users who are not particularly adept at programing languages. To describe it
in further detail, Apex is more so for large-scale applications and high user loads,
making it suitable for enterprise-level deployments as while it can work for a small
business, they would not have an easy entrance to approach Oracle. Meanwhile,
many more users are familiar with Microsoft and its user interface.
Security
There is also the matter of the security of the two low code solutions as this
is an important aspect for any business where they need to store their data and have
their employees using these applications. Access has basic security features like
user authentication and password protection but may not be sufficient for highly
secure applications essentially it is pretty easy to access the Access data once you
have a user's password. Meanwhile Apex has much more solutions for companies,
it offers robust security features, including role-based access control, encryption,
and auditing, in addition to the authentication features provided by Oracle such as

password and multifactor authentication. making it suitable for sensitive
applications.
Conclusion
This paper covered the boons and banes of two of the best low code
applications Apex made by Oracle and Access brought to us by Microsoft.
Primarily by viewing their performance capabilities, history, and usage for various
organizational needs. As stated, there is Microsoft Access that is user-friendly it
has a more limited scalability that makes it harder for large enterprises to be able to
actively use it. Meanwhile, Oracle Apex has a larger feature suite and is designed
to be able to be used by multiple users, making it a superior choice for
organizations with complex data management requirements. By examining their
architectural differences, performance capabilities, security features, and suitability
for various organizational needs, this paper will provide insights into the trade-offs
involved in choosing between Apex and Access. Ultimately, the choice of database
system depends on the specific requirements of the organization, including the size
and complexity of the database, the number of users, the level of security required,
and the budget constraints.

References
InterSoft Associates. “Risks of Using Microsoft Access for Your Business Database.” InterSoft
Associates, https://intersoftassociates.com/articles/migrations/risks-of-microsoft-access/.
Lenovo. “What Is Microsoft Access? Advantages & Security Tips.” Lenovo,
https://www.lenovo.com/us/en/glossary/what-is-microsoft-access/. OpenGate Software.
“What Is Microsoft Access Used For?” OpenGate Software,
https://www.opengatesw.net/ms-access-tutorials/What-Is-Microsoft-Access-Used-
For.htm.
Simplilearn. “What Is Microsoft Access: Overview, Features, and Uses.” Simplilearn,
https://www.simplilearn.com/what-is-microsoft-access-article. Accessed 8 Dec. 2024.
Microsoft. “Access.” Microsoft, https://www.microsoft.com/en-us/microsoft-365/access.
Oracle. “Monitor Data Storage and Manage Capacity Usage.” Oracle Help Center,
https://docs.oracle.com/en/cloud/saas/iot-production-cloud/iotpp/monitor-data-storage-
and-manage-capacity-usage.html.
Apex Community, (2024, July). Apex History. History.
https://apex.oracle.com/pls/apex/r/apex_pm/apex-community/history
Trust Radius. (n.d.). Compare microsoft access vs oracle apex on trustradius: Based on Reviews
& More. TrustRadius. https://www.trustradius.com/compare-products/microsoft-access-vs-
oracle-apex#community-pulse

Oracle_vs_MicrosoftAccess_paper.pdf_____

Recommended

More Related Content

Similar to Oracle_vs_MicrosoftAccess_paper.pdf_____ (20)

Recently uploaded (20)

Oracle_vs_MicrosoftAccess_paper.pdf_____