Great. Thank you very much

Thanks Dave. I will try this.

Thank you very much

Thanks.

:)Thanks

Create a new class and implement that interface. There won't be a class generated for it because the parameter is an interface, unless your COM library exposed a class that already implements it elsewhere. -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----

Did you read the links I gave you? They discuss localization in great length. First, if you are authoring the original forms in Spanish and it is in that locale that all your code is contained, then use the NeutralResourcesLanguageAttribute and specify the appropriate culture. Second, try going back to the "default" culture (actually the neutral culture) in your form designer and compile again. VS.NET might thing that you're trying to compile the English satellite assembly as the primary assembly. Second, show hidden files in your project. Look at the ResX files. If you use VS.NET's designers, these will be hidden under forms. If your form source file is named MyForm.cs, then you should have a MyForm.resx (the neutral language) and MyForm.en.resx or MyForm.en-US.resx. -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----

Use the SelectedText property. This[^] may also help. Regards, Alvaro Can I ask you a question?

The alternative is to have your globals as static members of some class. That way they can be accessed anywhere. Nish Extending MFC Applications with the .NET Framework [NW] (coming soon...) Summer Love and Some more Cricket [NW] (My first novel) Shog's review of SLASMC [NW] Come with me if you want to live

Slaru wrote: someone Me Slaru wrote: told me that linkers are stupid No, I told you preprocessors are stupid. Somewhere in windows.h there is a preprocessor directive to turn every MessageBox into MessageBoxA or MessageBoxW, depending on whether it is a Unicode or non-Unicode build. Now, the *stupid* preprocessor does not know that your MessageBox is .NET MessageBox and not Win32 API MessageBox, and it turns System::Windows::Forms::MessageBox to System::Windows::Forms::MessageBoxA.

in any cases, before app (a process) destroys, all threads created by the app should be destroied. if not, often (not always) exception happends. wait a while, check thread's status, i think it will help. :rose: :rose: :rose: :rose: includeh10

I have solved the problem, I add this line AFX_MANAGE_STATE(AfxGetStaticModuleState())