VBLM does not extract strings that are directly assigned to any property on this list, whether the assignment occurs in the definition section of a control container or elsewhere in code.
What's the point? If you look in the form definition section of a VB form file, you'll see that there are many form and control properties with string values that you would seldom, if ever, want to translate. These properties -- LinkTopic and DatabaseName, for example -- are used internally. Translating them is undesirable as well as unnecessary, because doing so will often cause errors.
VBLM supplies a lengthy default list that includes the internal string properties of all controls supplied with VB3-5.
Note 1: You will seldom need to remove properties from the list (maybe Tag depending on how you use it, FontName if you're translating across character sets), but you will want to add any additional internal string properties of your custom controls.
Note 2: "Assigned" is in quotes because VBLM won't extract strings if they are simply to the right of properties on this list with an "=" in between. Thus VBLM will not extract "readme.txt" from the following code, even though it isn't an assignment:
If CmDialog1.FileName = "readme.txt" Then Beep
Note 3: The default properties list is expanded from VBLM4, but, if you've upgraded, you won't get the new default entries unless you a) installed into a new directory, or b) manually remove or comment out the IgnoredProperties key in the [StringExtraction] section of VBLM.INI
See Also