So what are the pros and cons of using Microsoft Access forms? Working with 'Bound' forms means that it's much easier and quicker to create forms that are associated to records from tables or queries saving on the development time. However, every time the cursor (that is when scrolling) moves between records, you automatically trigger the save record action maintaining data integrity. What if you wanted to stop this from happening and have better control? Well, you can't with this type of object relationship.
The number of controls from the main form coupled with a large volume of available records lends well to Microsoft Access forms being unbound. Another Tip for you! If you are designing your database to be shared with others (multi_user system), then you will probably want to split the database between the 'back_end' and 'front_end'. The interface (or front_end) will best served using unbound forms to help with network traffic and general performance too.