>>Also, I have one main method in my form that handles adds, modifies, and deletes for DBF tables. Currently, all my applications update data via a forms and toolbars. Should I move this method to a visual class library so that non-form objects can access it? These are just a couple issues on my mind.

I believe that the business class concept (ala codebook) encompasses the functionality that you are looking for. Rather that placing the code that handles data for an entity (usually one table) in a form, place it in a non-visual class that can be placed on any form, or called from another procedure.