>It is always a good idea to check the framework once in a while.
>
>Yesterday, for example, I found that I now don't have the need anymore to take care of the Window menu. I removed about 80 lines of code, 2 methods and various lines in and there. It reduces the code and speed to runtime.

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.

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.

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.