Glen,

>Is the localization functionality part of the "smaller, yet important" things?

I knew someone would ask this <s>!

MM .NET 1.1 has a new mmMessageManager class that is used to retrieve localized text for message keys from a new Message table. However, if you don't turn on localization in your app, you don't need this table.

At run time, a localization flag is checked by the Framework. For developers who don't localize their apps, MM .NET has hard-coded English strings that are displayed. If localization is turned on, rather than using these English strings, a call is made to the new Message Manager class instead and the text to be displayed is retrieved from the database. Developers can use this same Message table to add strings and MessageBox information for their application-level needs.

The reason I didn't mention this is because, although the necessary MM .NET components are in place, an end-user interface for translating user interface elements (ala MM VFP) is not...we need to release version 1.1 very soon, so I'll delay the end-user localization UI until right after the 1.1 release, and I'll make it available to developers who are interested at that time.

Regards,