Action Scripting

[fairviewcomputing]

I want to attach a script to an event on the form. I right click on the field to which the event is to be attached. I select "On Change" from the drop down menu. Using action scripting, I select "Value Get". From the drop down window I select from the list "Field86" and assign it to a variable. I get an error "No such field", even though I selected it from the drop down list.??? What am I missing here?

[forskare]

RE: Action Scripting

Howard,

I tried to duplicate your error message but I can't get the variables to show up in the variable drop down box. Makes no difference if the variable is Layour, Session or global.

Anyone know what the trick is to get the variables to appear in the variable drop down box when defining a GetValue?

Thanks,

kenn

[Tom Patten]

RE: Action Scripting

Howard,

Is the variable visible? Was it declared on the form using the "V" symbol, or did you dim it in the script. You should end up with something like this:

Try this on the button:
yourvariablename = field86.value
yourVariable.refresh()

I usually place the variable on the form to watch it work, then hide it.

Tom

[forskare]

RE: Action Scripting

Tom,

I declared my variable with the "V". That is supposed to work, right?

kenn

[Tom Cone Jr]

RE: Action Scripting

Howard,

I'm unable to duplicate your issue here. Is Field86 a field on the form, or is it embedded in an object on the form?

Is Field86 a field in your table, or is it a calc display field which exists only on your form?



Ken,

Action Scripting Value_get() doesn't seem aware of shared or global variables. You just supply a variable name and it's used local to the script.

I think you'd have to convert code to xbasic and redeclare the variable if you want to assign value from an object on the form to a shared or global variable on your form.

-- tom

[forskare]

RE: Action Scripting

Yah, it's a bit confusing, isn't it? One would think that, from the way it's set up, the variable names are suposed to be listed. Otherwise, why have a drop down box? Why not simply instruct: "Enter variable name here"?

Not a big deal for me. I came across it when taking a look at Howard's issue.

kenn

[fairviewcomputing]

RE: Action Scripting

Tom, Field86 is the name assigned to a Type-In field on the form that is a field in the "Hours" database. As for seeing the variables in the drop down box, I defined them under the "Variables" tab in the code editor. Not being trained as a programmer, I don't know what you mean, "Embedded in an object on the form"??
The name "Field86" is what I see when I right click the field and select properties.

[fairviewcomputing]

RE: Action Scripting

Tom, it is attached to the "On Change" event for that field (Field86). When I tried your code I got a "No such field" then "Incorrect data type". These messages came up right after I applied a change to Field86.
Howard

[Tom Cone Jr]

RE: Action Scripting

Howard, I didn't mean to be obscure.

This script works fine here in the OnChange event for the 'NAME' field on my form:

dim shared currname as C ' declare the variable
currname = NAME.Value ' retrieve value from Name field
' and store it in variable
trace.writeln(currname) ' write the contents of the variable
' to the trace window

If you want to use this in Action Scripting,
insert a command for Inline Xbasic Script, and type it in
with the following provisos.

To use this in your form, substitute the name of your variable for 'currname', and substitute your field name for 'NAME'.

If this doesn't help, post your database online, or email it here. Please include a simple text file explaining which form and field(s) are involved, together with keystroke by mouseclick instructions for what you are seeking to accomplish.

-- tom

[fairviewcomputing]

RE: Action Scripting

Tom, I didn't mean to imply that you were being obscure, it's just the fact that I am familiar enough with xbasic to be dangerous...Ha. It seems that everything I try lately ends up with an error message. One of the problems that I generated during these discussions was the fact that the names "Field12" etc. names are OBJECT names, not field names. What threw me was the dropdown list in the action scripting that listed all of these "objects" that I took to mean "fields". Apparently it doesn't work that way. That leads me to wonder why show the drop down list if you can't use it to define the field on which you wish to act??? Maybe version 5 books will help. Thanks for your interest and help. I really appreciate this forum and all of the helpful persons in it.
Howard