Spam808 - June7's answer is correct. So the question is, on that other form, how does the form get the value to be displayed? If it is computed on that form, how is it computed and from what? If it is just displayed, that's a different question.
You might need something as simple as a DLookup but if there are multiple inputs to a computation then you might need more.
Remember that if a form isn't open, it isn't in memory. The syntax you used (that starts with [Forms]) implicitly is looking in memory, because the [Forms] collection only contains open forms; no closed forms are there. To read the contents of a control, that control has to be instantiated by OPENING and LOADING the form that contains it.
Further, that strategy is dangerous in another way. Forms are independent from each other with the one exception being a parent-child form (or if you prefer, a main/sub form) situation. If both forms have the possibility to navigate to different records, there is no guarantee they will be synchronized to the same record unless they are explicitly linked, and that can only easily occur with parent/child form situations.