Gee this is generating a lot of mail

Ok Classes. I use them to define individual tables in a database, one class per table. This then allows me to insert the class where needed, in the same project, in different projects without having to re-invent the wheel. Kind of the ultimate reusable code. The same applies for dll's consisting of standard functionality that l will use in just about any project.

What you end up with is a kind of code library, similar to the includes our C colleges spend years developing.

As for my hellish app, only some one with very little vb knowledge would have produced that piece of garbage. Talked to the client's about it last night, and they have agreed to finance a complete rewrite...yahoo. So spent four hours over night in design, and will present to clients today And that is when coding gets eaasier, design specs before cutting forms and modules