When you click the Files tab on the SX Options window, VBLM shows you a multi-select list of all code files in the VB project that is, or is about to become, the parent of a VBLM project.
The Files tab is visible only when VBLM knows about the files contained in a VB project. That's why, when you select File/New on the main window, VBLM reads and interprets the VBP/MAK project file before asking if you want to adjust SX options.
When you select files on the Excluded Files List, you are instructing VBLM to ignore them during both the string extraction and build processes. VBLM neither extracts nor replaces any strings contained in selected files. In fact, because the "translated" versions of these files will be identical to the originals, VBLM lets you include the originals in the translated project instead of making copies (see Build Options: Excluded Files).
If ALL of the strings in a particular VB project file are for internal program use and should not be translated -- say, for example, that you've put all of your SQL queries in their own code module -- then excluding the file is the fastest and easiest way to exclude the strings. Keep in mind, though, that if there is even 1 string in the file that should be translated, you don't want to exclude it.
VBLM stores excluded file information in the LMP file, so it is retained over time.
See Also