Microsoft Access Forms - associated or not associated?

Microsoft Access Forms - associated or not associated? -

Microsoft Access is designed for rapid development of applications. A wizard module enables the development of fast and easy application using the Bound modules. The bound form requires little or no programming, and is ideal for the amateur programmer.

The Unbound module requires the use of VBA (Visual Basic for Applications) and ADO (ActiveX Data Objects) or DAO (Data Access Objects) to retrieve and update records.

A Microsoft Access form can have a mixture of fields that are associated or not associated.

The bound form

The Bound form has fields that are connected directly to a database table. Any change to a bound control on a form is immediately updated in the corresponding field of the current record in a table.

The characteristics of the bound form include:

• The module can be configured quickly and easily using the Form Wizard
• The module is a Find, filtering and sorting facility
• the module indicates the number of records and a navigation bar
• module allows the selection, addition, deletion or modification of records
• Under the modules can be installed to handle one-to-many

the disadvantages of bound form

the problems are:

• the default behavior of access can be unacceptable to users - such as automatic saving of fields or records
• cancellation of an update with the Esc key is not easy to use
• there may be performance issues when handling data from the back-end database
• there is the need to explicitly control record locking
• Access error messages are user
• It 'hard to convert to VB.Net bound form
• E' difficult to extract the business rules from the module logic
• Canceling a switch to a field or record may be difficult
• there is no precise point at which a record is saved
• loads network can become a problem
• There is an overhead when combined form is kept open for long periods
• the logic of a bound form can get pretty complex

the combined form validation is done field by field, using the first update event. When the validation involves multiple fields, this is not the easiest way to ensure that the clean data. Multiple events can very easily call each other several times, which can be difficult to cure.

The Form Unbound

The Unbound module provides a better solution and more professional. It is a need for greater efficiency, to extend the number of users and to provide a better control of the application.

The advantages of the unbound form are:

• There is more control in reading and writing record
• There is more control over editing, saving and deleting records
• records can only be updated when all fields are valid
• not user-friendly error handling
• there is greater efficiency in the access logs
• Reducing competition problems (record in problem drug use)
• the integrity of the data can be guaranteed
• the Unbound form is readily converted to a VB.Net project
• Conversion of the back-end database to SQL Server will be easy

In summary

for simple or one-off applications, the bound form is ideal. It can be configured and running in minutes.

For a system of administration Company, in amulti-user environment, the additional work in authoring logic theVisual basis of an unbound form, it will be time well spent.

Tweet