which version are you running ? FMP 14 came with the Script Workspace, previous versions worked differently. Are you using Windows or OS X.
1 of 1 people found this helpful
just info ...
I'm using FM14 on Windows.
ctrl-shift-S will pull up the Script Workspace window, even if it's minimized.
A star next to the script name indicates that a script is unsaved.
I am using V14 and OS X (latest and greatest)
Please let me clarify a little...
"Scriptspace" is "not available" to me in all situations on all forms. I might have full access on some forms successfully building, editing and attaching scripts to forms on SOME forms and then all of a sudden, I change forms, and it is gone or EMPTY! Then some of the scripts I previously attached to buttons on other forms may or may NOT work. I am really stumped! Any ideas???
I know that using Custom Menus can hide/prevent functionality. For example, if the Help menu is hidden, then F1 does nothing (normally Help), etc.
Sorry, I should've just said, "can you see the Scripts menu in the menu bar?"
Good information to know! I’m not usingg that …yet… but I’m grateful to know this! Thanks David!
1 of 1 people found this helpful
This may be a silly question but do you have only one file open? This is exactly the behavior you'd expect if you were going back and forth between two or more files, especially if you didn't have script writing privileges on one of them. Scripts are attached to a single file, so you can only see the scripts of the current file.
Multiple files open….wasn’t aware that was a problem…is it?????
It's not a problem, you just need to keep track of which file you have open. Scripts created in one file one show in the workspace opened for another. Use the Window menu to select the correct file first, then open the scripts workspace for scripts on that file.
The other thing to be aware of is that the Script Workspace will display the file name and the server name in its top bar:
eg. "Script Workspace (FileName (ServerName ))
Phil's absolutely right; when I looked at my response above I realized I misworded it. To expound a bit on what Phil said, because you're a newbie:
Each Script Workspace window, and the scripts it contains, is associated with one particular file. You can keep several Script Workspaces, from different files, open at once. This is not a problem except that you can get confused by which Workspace is associated with which file - that's why your scripts are 'disappearing' - you're just looking for apples in the bin that holds oranges. The Script Workspace associated with a particular file has the name of the file listed in its header, upper left corner.
One way to make this less confusing is to close the Script Workspace for the file while you're doing non-scripting stuff. Then, as Phil says, select the file you're interested in scripting for, making that the current window. Now when you select Script Workspace you'll see the Workspace for the current window (which is what I was awkwardly referring to in my last sentence above).
The "Scriptspace not available" problem is what I was referring to when I talked about write privileges. The author of the file can set privileges so that people without the right account name/password can't write scripts. You probably had as the current file another file, with such restrictions, when you ran across that dialog box.
Does that help?
Yes…it DEFINITELY does! Thanks for clarifying!