People in some industries routinely refer to number of thousands in terms of "K". In other words, 1K is the same as 1,000, 3.6K is the same as 3,600, etc. I've written an auto-enter calc in a number field to handle the conversion of the number in terms of "K" to the real number, i.e. a user enters "3.6K" in the field and the auto-enter calc changes it to "3,600".

Here's where the challenge comes in...I'd like the field to initially behave as a lookup from a related field, and then, if the user wishes to change the looked up value, I'd like the user to be able to enter values in terms of "K" and then have the auto-enter calc convert it. Is this possible???

Wow, talk about wanting to have my cake and eat it too! :o

Sure.

Have your field that they enter the "K" value into be a different field, then have the number field be the auto calc that does this.

If you did your auto calc right, it shouldn't matter if they put in

3,600 3600 or 3.6K, your calculation should always return 3,600, but the field they inserted the "K" value into will always stay how they put it in, allowing them to change it when they want.

Probably an easier way to do this, but this seems like it would work great to me.

You could do a conditional auto-enter calculation.

If(IsEmpty(Field);Lookup(...);DoYourCalc)

Make sure that you allow the existing value to be replaced.

Lookup and auto-enter are mutually exclusive. But there is another way:

LookUpAndAutoEnter.fp7.zip

Thanks to all for the solutions offered. None of them do exactly what I want so I've decided that the best way to handle this is to set the field by script upon creation of the record, and then I can user the auto-enter calc as I wish.

But...the solutions you've all offered give me ideas on how to handle other unrelated issues. Hmmm, always learning something new from FM Forums!