When the Log String Extraction option is checked on the logging tab of the general options window, VBLM logs all SX operations as you create and update projects. The disk file (VBLM Extraction Log.txt by default, but you can change this), is written to the same directory as the parent VB project. If the file exists, VBLM handles it per your setting on the logging tab.
The extraction log grows quickly because it contains the following information for each line of VB project code that contains a string:
1) The line number and the section or procedure.
2) The code itself.
3) A list of strings extracted, if any.
4) A list of strings not extracted, if any, and the SX options that excluded them.
For example:
C:\VB3\SAMPLES\ICONWRKS\ICONEDIT.FRM
Line 2410 (Prepare_For_New_Icon)
Code: Caption = "IconWorks Editor: " + Format$(CurrentIcon + 1) + " - " + UNTITLED
Extract: "IconWorks Editor: "
Ignore: " - " (Punctuation)
Extraction logs hardly qualify as interesting reading, but the logged information can be quite useful to help tune VBLM's extraction options to best match your project. See Tips & Tricks for more info.
See Also