I have a button that performs a Send Event function. I only want this function to be available if a txt_complete field has a value of "Complete"

Is there a way to have the button be inactive or greyed out unless the value of the field is like above?

This would be similar to the way many websites disable a "Continue" button unless you check a "Accept agreement" box.

Thanks for any help

I have a button that performs a Send Event function. I only want this function to be available if a txt_complete field has a value of "Complete"

Is there a way to have the button be inactive or greyed out unless the value of the field is like above?

This would be similar to the way many websites disable a "Continue" button unless you check a "Accept agreement" box.

Thanks for any help

I have a button that performs a Send Event function. I only want this function to be available if a txt_complete field has a value of "Complete"

Is there a way to have the button be inactive or greyed out unless the value of the field is like above?

This would be similar to the way many websites disable a "Continue" button unless you check a "Accept agreement" box.

Thanks for any help

Deego:

In the script attached to the button, you can verify if the text box has the right value, and either continue or exit your script.

-Stanley

Deego:

In the script attached to the button, you can verify if the text box has the right value, and either continue or exit your script.

-Stanley

Deego:

In the script attached to the button, you can verify if the text box has the right value, and either continue or exit your script.

-Stanley

AH! I wasn't thinking of it like this. This works perfectly, thank you!

AH! I wasn't thinking of it like this. This works perfectly, thank you!

AH! I wasn't thinking of it like this. This works perfectly, thank you!

Another very powerful technique is to use self-relationships and portals to hide interface elements.

Check out the "More visibility" example discussed here:

http://www.fmforums.com/threads/showflat...1/o/all/fpart/1

It's quite amazing when you see it in operation.

Another very powerful technique is to use self-relationships and portals to hide interface elements.

Check out the "More visibility" example discussed here:

http://www.fmforums.com/threads/showflat...1/o/all/fpart/1

It's quite amazing when you see it in operation.

Another very powerful technique is to use self-relationships and portals to hide interface elements.

Check out the "More visibility" example discussed here:

http://www.fmforums.com/threads/showflat...1/o/all/fpart/1

It's quite amazing when you see it in operation.

Also, you can use a calculation field to set the color of its own text (black vs. grey) depending on the values of other fields. That calc field can be part of a button with a script that checks the same field value the calc uses. This way, you can have a visible button which is greyed out and doesn't do anything, or is full black and does what it purports to, depending on whatever criteria you want.

Also, you can use a calculation field to set the color of its own text (black vs. grey) depending on the values of other fields. That calc field can be part of a button with a script that checks the same field value the calc uses. This way, you can have a visible button which is greyed out and doesn't do anything, or is full black and does what it purports to, depending on whatever criteria you want.

Also, you can use a calculation field to set the color of its own text (black vs. grey) depending on the values of other fields. That calc field can be part of a button with a script that checks the same field value the calc uses. This way, you can have a visible button which is greyed out and doesn't do anything, or is full black and does what it purports to, depending on whatever criteria you want.