Script Buttons Not Working

[aesart]

Now that I've done a search and didn't find a match, I'm worried that I'm the only one...

While developing a database, I'm having a strange problem with FMD 6.0v3, where I can create a script, and run it using the ScriptMaker and the keyboard shortcut, but if I create a button, no matter what I have tried, running the button in Browse mode keeps giving me an error message that the script is either broken or missing. I've tried this with different solutions, trashing preferences and repairing permissions, but I'm baffled... Anybody else seen this behavior?

Quicksilver 2002, Dual 1GHz, 1GB Ram, Mac OS X 10.2.3, FM Developer 6.0v3

[Lee Smith]

Hi aesart,

Boy would this be a major bug if it were true. I've had similar problems in the past, maybe one of these scenarios will help you. One would be when there was a previous script attached to the button, and the button has many parts, I would be assigning my new script to one part, but I actually hadn't remove the old one, and it was attached to a different part. The old script would always run instead of the new one. You can check this easy enough, by trying to ungroup the button, and if it was grouped with the script attached, it should make FileMaker tell you that "if you proceed, it will remove the script from the button." Great, ungroup that's what you want anyway. If this doesn't work, then the other thing you can do is to check each part of the button (assuming it is multiple parts), against the Format - Button, to see if one of the loose parts has it assigned. I have also had to move the parts of the button all over the place so as to get to them. If this works, then reset the button to the new script.

The second scenario is more embarrassing, it's when I keep assigning the button, blush, with the same bad script. This can sometimes happen if you have scripts of similar names, and of course, that script will always be the broken one.

HTH

Lee

[aesart]

Oh, if I could ever think of trying the obvious... Lee, thank you! All I had to do was delete the button and make a new one (duh!) - works fine now...