Digital Workshop

I am doing a simulation/training program on one of our company programs known as the Rig Asset Management System (RAMS). I ran into one of those silly little things that seem to catch me unawares. I needed to be able to capture user input in text boxes and then display the completed work order later. Seems simple enough, just set up a text input box and capture to a variable file, then read that file into the screen when they hit "Close Work Order." However, two things are happening which I do not know are related or not. For one thing, when I test the text input boxes show the title of the variable :"[ILMObject WOTitle]" for my variable "WOTitle." This is text that can be edited or erased, but obviously not something I want shown. Actually, the help files make a big point that it will NOT show. Then, succeedning the screen with the text box that is to show the variable "<WOTitle>" does NOT show the text. It is empty. Where is the variable file written so I can check to see if it is created? Why isn't it showing?

What's up with that?

Dave

It sounds as though you have a variable and an object with the same name - this will cause the name confusion you are seeing. Rename the clashing object.

Also, I may be misunderstanding what you are doing, but you do not need to write the variable contents to a file - you can just use the variable on a later page (assuming it is a publication scope variable and not a page one).

Mallette

I think Duncan is along the right lines with the naming of objects being the same as a variable. This foxed me for a while as well. Att. is an example of what I mean. The text input box + variable works perfectly when the names are different.

Hope this helps.

Clive Cartmel

Hi Clive,

Delete text field WOTitle2 and add a new Input field with input variable WOTitle2.

Cheers

Ronnie

I've been off a few days as we work 10, 5 off.

Thanks to Duncan and all. All correct. I wonder, however, how I'd ever have known this and how many others do not? It is not intuitive in the sense that these are two different things entirely and the intuitive thing is to name them the same as they go together to make a whole.

Dave

General rule when using any programming language or application -- never give two objects (of any kind) the same name.

Paul