Access Program with an Access Database
An Access/Access application may be a good option if you will be not be managing
a large amount of data and will not need to access the database remotely. This
is often the most cost-effective solution for in-office applications running on
a local network.
Advantages
Less Expensive than an ASP.Net/SQL or Access/SQL Application - Building
an Access front-end takes much less time that building
an ASP.Net front-end. Access provides a larger number of built-in features
and designing tools that speed
up the process.
Adequate to Quickly Perform All Necessary Tasks in Many Situations - If you
are not managing a large amount of data and do not need to access your database
remotely, an Access/Access application may be completely adequate for your needs.
No Need to Purchase Additional Software - Access Programming Services will
provided a licensed runtime version of Access with your application. The runtime
version drives your application, performing all the tasks needed, but cannot be
used to add features or to re-design the application. Using a runtime version
of your workstations is a good idea because
it runs faster than the full version,
and users cannot tamper with the application's code.
Disadvantages
Intallation Issues May Occur - If all of your computer workstations
are fairly new and have a recent version of Windows installed, installation should
run smoothly. In some cases, with older computers with a different version
of Windows on each computer, some annoying installation problems can occur.
These are not insurmountable, but can be time consuming.
Greater Load on Your Network Server's Resources - The always-connected
approach used for this application type can slow down the server and, consequently,
your application.
Limited to about 12 Simultaneous Users - The maximum practical
number of concurrent users for an Access/Access
application is about
twelve users.
Response Time Slows as Database Grows - With this application type,
the application will respond more slowly as the database grows. This issue
can be managed by deleting unused records and following other data management procedures
to keep the database from growing too large. If the database grows past a
certain point the application will need to be redesigned with a quick connect/disconnect
apporach or changed to an ASP.Net/SQL or Access/SQL application. It's important to note
that for many applications, database size will never be an issue.
Remote Connections More Difficult - You can
connect remotely
with an Access/Access application, but not as easily as with an ASP.Net/SQL application.
The remote connection for an Access/Access application will require a Virtual
Private Network setup or some other type of remote access procedure.
Examples
Example 2: Tour of an Access Application - Wound Management Software
Example 1: Screen Shots from an Access/Access Application for Water Filtration Companies
Previous Page
Next Page
Click on one of the links below to see samples of Access/Access applications developed
by Access Programming Services. The example windows will appear on top of
this window. Check your 'Pop-Up Blocker' if nothing happens when you click
on one of the links.
The first example displays screen shots from an application developed for companies
that sell water filtration equipment.
The second example is a walk-through tour of a medical wound-management software
application.
