General discussion

Locked

Microsoft ACCESS Bound vs Unbound Forms

By idi ·
I would like some insights into the advantages/disadvantages of bound versus unbound forms in Microsoft ACCESS applications. Also, quidelines as to when to use one or the other would be appreciated.

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Microsoft ACCESS Bound vs Unbound Forms

by donq In reply to Microsoft ACCESS Bound vs ...

Essentiall all Forms are unbound however Microsoft refers to forms that glean the values that populate their fields as "Bound" forms. These forms have Fields that are linked to a Table or Query as their data source. (Any form used for data entry /editing is generally considered a Bound Form.

An application desktop the Access Wizard builds would be considered an "Unbound Form" because it doesn't have any data entry forms.
I use Undbound Forms to pop up custom Help windows, application navigation forms, and occasionally a query filter form wher the user doesn't enter anything. On a filter form they only "select" existing entries that we entered earlier through a Bound Form.

Hope this helps. Don Quigg.

Collapse -

Microsoft ACCESS Bound vs Unbound Forms

by idi In reply to Microsoft ACCESS Bound vs ...

Poster rated this answer

Collapse -

Microsoft ACCESS Bound vs Unbound Forms

by Bob Sellman In reply to Microsoft ACCESS Bound vs ...

To add to the previously posted answer:

Here are some guidelines for when to use bound and unbound reports:

An unbound form (no associated table or query record source) works for menu type forms where, for example, you have a number of buttonsto allow the user to make a choice of an action.

You can also include controls where the user enters data which will be used for application activities, but not for direct entry into records in a table (which is when a bound form is used). Examples of data for application activities could be some of the following:

Log in form: enter userid and password. You then could use VBA code to check the entered data against a list/table of valid entries and either let the user continue or force an exit from the application.

Report menu form: enter various parameters required for reports on the form. When a button is selected to run a report, the parameters will be used to generate that report, either by being criteria that are part of the query used as the record source for the report or used in VBA code to build a filter clause which you use to open the report with, for example, a statement like:
DoCmd.OpenReport "rptThisReport",acViewNormal,,strFilter
(strFilter would be the filter clause).

Note that a bound form which has the Allow Additions property set to False will not display anything if you have no records in the table/query set as the record source. I mention this because it can result in unexpected results if you do not plan for it.

Collapse -

Microsoft ACCESS Bound vs Unbound Forms

by idi In reply to Microsoft ACCESS Bound vs ...

Poster rated this answer

Collapse -

Microsoft ACCESS Bound vs Unbound Forms

by idi In reply to Microsoft ACCESS Bound vs ...

This question was closed by the author

Back to Web Development Forum
5 total posts (Page 1 of 1)  

Related Discussions

Software Forums