>I have notice that I do not use some methods and classes in every application, but they are part of my application library. Originally, I thought the best way to design class libraries was to not have too many of them. Now, I am thinking maybe I should put these classes in a separate library. This would mean I could have a library with one class.

I have a few VCXs in my framework. Then, when building an application, I can have some new VCXs which can include some subclassing of the main framework classes.

>Some other things I have been reviewing are how I handle errors and how I update tables in a DBC. I catch errors in my Error event and display a message to the user. Trapping the errors are not a problem, rather what to do after display message is a concern. Should I quit the application? It would be nice to see how others handle errors.

Error messages, in my case, advice the user and quit the application after.

>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.

All those are in my baseform classes. If you have to do a process which need to deal with those but there is no form, you may define a form, do your process in the Init() and RETURN .F. at the end. You may also move the form outside the desktop area and avoid RETURN .F. in the Init().