You can use the documenting wizard to get the count for forms, vcx's and prgs. Like Craig said though, that won't get you the reports. I agree with Craig that LOC are not as effective a way to measure OOP code as they were to measure procedure code. (How many times do you count a base class if it runs every time you instantiate a text box? etc.) That said, one of the first things I do on a new maintenance job is run an LOC listing so I can get a rough idea of the size of the beast.

When you run the documenting wizard, select the option for a Source Code Listing. Tell it to send everything to one directory (C:\temp). When it's done, open the file YourProjectName.lst (where YourProjectName is the name of your project) and select Show Column/Line position from the RightClick options menu. The .lst file will be one giant listing of all your procedure code from programs, vcx's and forms. It even adds a LOC for each property setting.

Good luck!

Marty