Expand my Community achievements bar.

SOLVED

New user question about dictionaries?

Avatar

Level 1

Hi,

Can anyone help  a new user on this?

I have looked, and Googled, honest! I can find very little.

I created a new form. In it I put a date field (todays date) on the field marker in design view there is an "i" at the top right of the field, hovering over it gives the message

"spell checking does not support this locale,  The spelling in this object or any child objects that inhererit this locale will not be checked"

WHY?

My pc locale is set ok, what does this mean? I also set the dictionary to UK

Any help - pointers, anyones assistance gratefully received.

Thanks McP

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

What is the system locale set to. The date and Time object will pick up that locale. Each object can have its own locale ...what is it set to on the Object/Field palette?

Paul

View solution in original post

3 Replies

Avatar

Correct answer by
Former Community Member

What is the system locale set to. The date and Time object will pick up that locale. Each object can have its own locale ...what is it set to on the Object/Field palette?

Paul

Avatar

Level 1

As far as I can tell, running Vista Business, the locale is set to UK, I can't see anything missing or odd. Unless I am looking in the wrong place. Is there a way to set the locale in Livecycle?  I could have missed that if there is one, new user as I said.

Very strange.

McP

Avatar

Level 1

Thanks for the info Paul,

I have looked at this again in the cold light of day (me not being tired)

The settings on the field were Locale: Viewers system locale. ( SO I thought it should pick up UK)

I changed it to UK and now the "i" has gone.

Thanks

Rob

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----