The rule is that the argument must resolve to string.

@FN returns a string.

"MyValue" in quotes is a string.

If you have a text element called Company, then you can pass Company without quotes, and Sesame will use the value in the Company element as a string.

If you actually want to pass the string "Company" rather than the element value, put it in quotes.

Etc.

Thanks for the info, but how about in FormFieldValue (which I use a lot).

The second argument requires quotes, but refers to the form and field names, such as:

formfieldvalue("LineItems", "Item sold", 1, part number)

It seems that only the last argument follows the rules you mentioned above.

???

Steve

In SBasic, all of the LEs generate an LE reference. So if you have a form with a LE called "First Name" on it - there will be a LE reference made for SBasic. This lets SBasic use the LEs and the values in the LEs as though they were ordinary variables. In most cases that is how they are used. But there a few operations - such as @RGBColor that want to operate on the LE itself - not on the value in the LE.

There are also some functions that take the name (not the LE reference itself) of a LE as the argument. This usually happen on functions that can operate on LEs that are not on the current form. If a LE is not on the current form (the one containing the SBasic) there is no generated LE reference - thus its name, a string, is used to indicate which LE on the other form is needed.

You can use an LE reference in that case - but it will use the value in the LE as a string, as opposed to using the string of the LE's name (unless, the name as string, is the value of the LE).

Bob, the formfieldvalue example is not part of an xlookup. It's used to 'post' data into a subform.

Mark, thanks for the explanation. It leads me to another question I have been wondering:

If I want to 'post' data to a field that is not visible on the form or subform, but IS a field in the current database I'm working in, MUST i use the xpost command or can I 'post' to it using a faster method?

For example, if I delete the "Item Sold" LE on the LineItems subform so it is not visible from the parent form, whats the easiest way to post data to that field from the parent form?

Steve

Quote:
I knew that Steve....I was making a attempt at humor, like "leaking pens"?....You were asking why the rule did not apply to a function that was not part of your original question, that's why I bolded xlookup..... ....enuf, back to work now, bye..........

Quote:


Don't delete it. Make it invisible and access it as you ordinarily would.

To "hide" subform fields in a TableView. make them narrow and put them at the end of the form.

Keep them on the subform, but move them to the bottom, and make them only a few pixels wide.  The position and the width you have on the subform is the sequence and width that will show up in the Table View. 

This will force those fields to the right in the Table View.  Now you can resize the subform to keep them out of sight.  You can also put a block on top of the scroll at the bottom, so no one knows that there is a scroll bar to those fields on the right that are out of sight.  Make the block the same color as the form background.