Running Script on Connected Volume

It would help to know what you mean by 'does not work'.

That could be any of:

does nothing

throws an error message

changes some items, but not others

changes items in the wrong way

Assuming it throws an error message, including that message would go a long way to helping identify the cause. There are so many possible failure states, it's hard to know which one is applicable here without more context, and the error message would help hone in on the issue.

As it stands, the script can't run anyway, so there's something missing. Specifically, the line:

			set label index of (every folder of folder jobsFolder whose name begins with eachJob) to 7

Nowhere in your script is 'jobsFolder' defined, so the script is going to throw an error at this point, unless it's defined somewhere else and you didn't include the whole script in your post.

You do say:

> The pathname of the folder is similar to

> /Volumes/Folder/Working Folder

but that's not defined anywhere in the script that I can see.

Assuming that's resolved somehow, you say it's a CSV file, but there is no parsing of the text file, beyond breaking it into paragraphs. This script could only work if the lines in the text file exactly matches the folder name, which likely precludes command-separated values, unless there's only one value per line.

That's why knowing the failure state and error message is important.

Too funny that it's my own script. :)

Shame the corner case of server-side files weren't considered at the time.

The error message goes a long way to clarifying what's wrong:

> Can't make file (alias "Macintosh HD:User:xxxxxxx:Tags.csv") into type file.

That means it can't find/read the Tags.csv file.

The AppleScript version is irrelevant here. That's about as plain vanilla as AppleScript gets, and there's nothing that relies on a newer version of AppleScript.

How, exactly, are you invoking this? You said you're running screen sharing to the server, and running it there? Any particular reason, vs. running it on your own machine over the network (not that I think it's critical to the issue at hand, though).

Do you only get the error message if you run the script on the server? or do you also get that if you run the script locally? Do you get any message/error when run locally?

I still don't see where JobsFolder is getting defined in the script. Is that the whole script?

> Below is the exact script from you. I'm not sure about the JobsFolder part.

Ahh, then I'm glad to know I'm not going crazy. The script you posted in the beginning is NOT the same as this script (or the one I wrote way back when). In your earlier post you missed this line:

-- Change this line to the path where your job folders are
set jobsFolder to "Macintosh HD:Users:yourname:Desktop:"

Which is kind of important, and is the exact thing I was saying earlier.

Now we have that straight we have a better chance of working this out.

I assume that you're changing this line when you run the script, since it's kind of locked to a specific folder. The big question is what you're changing it to.

When you run it on your machine, and are trying to change files on the server, it should look something like:

-- Change this line to the path where your job folders are
set jobsFolder to "Server Volume:Folder:"

Where 'Server Volume' is the name of the server as seen on your Desktop, and 'Folder' is a folder on that server.

If you're running the script on the server itself, then the path will need to reflect where the files are. They're not likely to be in some user's home directory, although that may be the case, depending on how you've configured file services on the server.

> When I run it on the folder with 2,000+ folders in it, it locks up my finder.

Yeah, the Finder really chokes when handed large numbers of files to deal with, especially on a remote volume. Kind of odd, really, since you'd think this is exactly what the Finder is supposed to do.

There is an alternative model I have that's a lot faster, that uses a shell script to dive under the hood, but it involves copying the label settings from an existing file (I've never managed to work out the right syntax for setting arbitrary labels ad hoc, so it's much easier to just copy what some other file has :) )

The good thing is that this model allows for multiple labels/tags (e.g. a file could be Blue and Green), which is something my original script never handled. Let me know if you want to give it a try.