Typical Access application

[John O'Conner]

What does the typical Access application look like? Does it run within
the Access framework? Do developers just develop the db in Access and
write their application in some other language (like VB, C#, or Java)?

I can't imagine developing an Access db and deploying an app that
requires the entire Access application to run it. Surely that's not how
it's done. Obviously I have something more to learn about Access.

 

[Sandra Daigle]

In addition to Kevins comments, I would offer a little terminology. Access
is just a tool for building database interfaces. Jet is the actual database
engine. You can use Access to build the tables and relationships and then
build the application in VB but then I'd call it a VB Application with a jet
Database.

Most Jet db apps that I've seen also use Access for the application layer.
I've seen a couple of VB apps and while they were functional, they were also
cumbersome because they couldn't take advantage of some of the data-centric
features that are built-in to Access.

Most of my users already have Access so deployment is not a problem but as
Kevin pointed out, the Developers edition solves this problem if you have
users who do not have/need Access.

 

[Albert D. Kallal]

The development language and tools available within the ms-access
development environment is quite amazing. You have the full VB IDE, and that
includes the ability to create class objects (you essentially have VB6...but
a different forms model).

Here is a article of mine outline the thought process I go through when
deciding to create class objects in ms-access:

http://www.attcanada.net/~kallal.msn/Articles/WhyClass.html

I should also say that a typical application takes all of the design skills
you can muster, and using ms-access does not get one off the hook of coming
up with a good design process. Here is some notes and ideas that I went
thought when deepening a application. In this case, I was converting a
existing application (from a mini computer) to one that was going to use
ms-access:

http://www.attcanada.net/~kallal.msn/Articles/fog0000000003.html


As for deployment, well, I mean any database system written in say VB and
JET does requite that the VB runtime be distributed, the JET engine be
distributed, and any additional libraries that you need for reporting
purposes. So, using VB, or c++ also means that a LOT of extra library's need
to be installed, and distrubied when talking about a database application
(there no such thing as a simple stand alone exe anymore!).

I would say that wide distribution of a access application is certainly more
of a weak spot compared to other development tools. However, it is certainly
doable with the developers edition of ms-access AND SOME 3rd party install
tools.

Last, but not least, you can take a quick rundown of the incredible tools
included in the office development system:

office fast facts
http://www.microsoft.com/office/developer/suite/fastfacts.asp

Note that the office developer tools are being moved into Visual studio
soon, but, the above link is still active!

 

[Guest]

If you get the Access developer's edition, you can bundle
your application together with the DB engine that allows
you to put your executable application on CD so that
ANYONE can run it, whether or NOT they have Access. And
there's no licensing fees so you can make as many copies
as you like to distribute!

 

[John Vinson]

What does the typical Access application look like? Does it run within
the Access framework? Do developers just develop the db in Access and
write their application in some other language (like VB, C#, or Java)?

I can't imagine developing an Access db and deploying an app that
requires the entire Access application to run it. Surely that's not how
it's done. Obviously I have something more to learn about Access.

<shrug> My clients seem to be quite satisfied. If you want to develop
a VB frontend to a JET database, and your clients don't mind paying
for twice or three times the development cost, more power to you.

 

[Van T. Dinh]

See comments in-line.

--
HTH
Van T. Dinh
MVP (Access)

What does the typical Access application look like? Does it run within
the Access framework?

Yes, Access database applications run in the Access "framework". Think of
Access as the GUI development tools. Access comes with the JET database
engine as the default database engine (and the MSDE for A2K or later) but
you can use other database engines such as MS-SQL, Oracle, SyBase as well.

Do developers just develop the db in Access and
write their application in some other language (like VB, C#, or Java)?

This in NOT a Access application. This simply uses the JET mdb file to
store data and accessing data through the JET database engine. If it is a
pure database application, be prepared to spend at least twice as long using
VB, C, etc ... compared to writing a database application in Access.

I can't imagine developing an Access db and deploying an app that
requires the entire Access application to run it. Surely that's not how
it's done. Obviously I have something more to learn about Access.

You don't have to imagine it, just go to a number of different workplaces
and see it for yourself. That's how it is done!

Most companies I do consultation and programming for already have MS Office
suite (I read somewhere that the MS Office contributes about 60% of
Microsoft revenue so you can work out the number of MS Office copies out in
the work-place) and with the Microsoft pricing structure, most places have
the Professional version which includes Access so the "entire Access
application software" has never been a problem for me. In addition, the
license fee for a few copies of Microsoft Office is probably fairly small
compared with my fee (or any professional database developer's fee), anyway.