One of my forms has reverted to the placeholders for the localization of texts. At least, that is what I think has happened. In the AutoDeleteMessage property the text is set to "Business_AutoDeleteMessage." It should say "Are you sure you wish to delete the current record?" Several of the properties have this behavior on the one form.



Business_AutoDeleteTitle

Business_AutoSaveChangesMessage

Business_AutoSaveChangesTitle

etc.



I have run into this before, but have forgotten how to fix it. I have searched the forums, but could not find where it has been posted. I think it is out here somewhere.



Thanks!!

Bill

Hi Bill.

Is this showing for the AutoDeleteMessage or for the AutoDeleteMessageKey? If the AutoDeleteMessageKey is ste, it overrides the AutoDeleteMessage property.

Hello Ivan,



The AutoDeleteMessage (and most other UIA properties of the form) is involved, not the key. This happened when I upgraded one time (I think). I just cannot remember what I did to make it work, again. I attached a picture...that'll help you see what I am talking about.



Thanks!

Bill

Is this form inheriting from a base form that would have those properties set?

Bill, what language region code are you using? Have you checked your localization project? Also, under the SF Solution Preferences, what is set for your Default Language?

The form inherits MicroFour.StrataFrame.UI.Windows.Forms.StandardForm.

I am using English (Default) for the language setting.

The region code is 1033.

The localization and messaging project hasn't been touched in months. It looks fine...the xml generated seems ok.



There are no other forms, that I know of, that are doing this. I have checked several.

It is wierd, since those are the internal message keys, and they are only used to get the messages from the SF language projects. If you reset one of them to default, what do you get?

After replacing each key manually, the text persists for each property. I have run the app, added and deleted a record and everything pops up just fine.



It sure would be nice to know how this happened. The default reason is, "It's a .NET thing."



There is a real reason, but spending time finding it may not be a good use of our time. Changing the properties has gotten the job done.



Thanks for your help, Ivan!

Bill

Any time, Bill!

If I come across any idea of why that could have happened, I will let you know.

Abraços.