[AccessD] The Famous Bound/Unbound Debate

There are a lot of reasons for choosing between bound and unbound Access
databases.

If you network is small self-contained, with a single data sources, small
data requirements, a stable environment and with simple independent queries,
it makes little sense to use any other configuration other than bound.

OTOH if you have hundreds of users (speed and accuracy is a requirement),
have multiple sources of data (like MySQL, MS SQL Oracle etc), you have the
BE MDB on server which boots occasionally or uses web-based (unstable)
connections or if you have groups of dependant queries (like a bank
transaction where a number of inter-related queries must complete without
error before a transaction is complete), in other words an industry level DB
then an unbound database is for you.

So why use the MS Access presentation manager; well simply because it is the
best simple and fastest front end builder.

Jim

      

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka
Sent: Monday, September 13, 2010 12:42 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] The Famous Bound/Unbound Debate

A lot of it was JC and I sparring.  LOL

I guess the essence is that bound/unbound is a 180 degree difference in
the approach of developing an application.

Bound forms in Access handle a metric ton of things automatically.  So
you are starting with a ton of features, and functionality, and end up
limiting, tweaking, or removing functionality.  

Unbound forms are the polar opposite.  There is not functionality at
all, you have to build everything you want to do from the ground up.

Bound design: 
Pros: Quicker to develop with instant functionality. Can be less code
intensive (depending on how much customization is done).  Access does a
lot of work for you.
Cons: More cumbersome from a mutli-user networked app.  If you need a
light weight form, you spend more time limiting functionality.

Unbound design:
Pros: Inherently more light weight.  Special functionality can be built
into, instead of on top of.
Cons: Longer development time.  More code intensive.  You replicate work
Access would do automatically in a bound form.

One big trigger to the debate was database/application design
preferences.

JC just brought up his 'call center' application, and a while back, we
had a discussion about one element of that application.

It was in a 'memo' field.  Let's say we had to track calls coming in to
a support center.  We'd have fields for caller, tech, date, time, issue,
categories, etc.  And a memo field for details not put into more
specific fields.

In a bound method, that memo field would be just that, one field, in a
table.  So as notes are 'added' to a ticket, you are modifying one
field, in one record.

In an unbound method, that memo field would be a separate table, with an
ID field linking back to the original table.  Each entry would be
timestamped (and stamped with the creator of the record).  You wouldn't
edit a 'comment', simply add a new entry.

There are pros and cons to both methods.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Brad Marks
Sent: Monday, September 13, 2010 2:03 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] The Famous Bound/Unbound Debate

All,

Compared to most of you, I am a relative newcomer to the world of
Access.

Over the past few months, I have noticed a number of references to the
Bound/Unbound debate.  It sounds like this was a really hotly contested
issue at one time and that now people almost joke about it.

For us newcomers, it would be nice if someone could explain this issue
at a high level and perhaps spell out the major pros and cons of each
side of the debate.

It is not my intent to start a Web-war, I would just like to better
understand what is going on here.

Thanks,
Brad  
The information contained in this transmission is intended only for the
person or entity 
to which it is addressed and may contain II-VI Proprietary and/or II-VI
Business 
Sensitive material. If you are not the intended recipient, please contact
the sender 
immediately and destroy the material in its entirety, whether electronic or
hard copy. 
You are notified that any review, retransmission, copying, disclosure,
dissemination, 
or other use of, or taking of any action in reliance upon this information
by persons 
or entities other than the intended recipient is prohibited.


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com