Dynamically open files on network volumes

[HazMatt]

We just bought a 120 GB Iomega NAS (basically a hard drive with an ethernet connection.) We plan on organizing our work files, organized by part number, on this new file server. The path would almost never be the same, because the script would be activated from different records in our parts.fp5 database.

I think this can be done, but I'm not sure how. This would have to be a cross-platform script, so I'm wondering about Windows vs. Mac file paths as well.

[Kurt Knippel]

Define your structure on the HD first. Then you can figure out how a given record can access it.

We do a similiar thing with photos on a network drive.

The structure of the drive is as follows: PhotoLibrary:ProjectName:Resolution:RollNumber:ImageName

So you might get PhotoLibrary:Jones:High:JON123:123A001.JPG

In the DB we simply use a couple of calc fields to determine the path.

[HazMatt]

Do you use a script to open the correct file? I've been messing around with the Send Apple Event script step, but that doesn't seem to work at all for me. Plus, this script step does not work on Windows.

[DykstrL]

On Windows you can use the format "My_serverMy_VolumeMy_FolderMyFile.FP5" to access the files. Use a Calculation field to set up the path, then use the Open URL script step to go to that location specified in the field.

An Applescript will work on the Mac side, but the volume must be mounted first - which can also be done with an Applescript as Captkurt described. Again. using a calculation field to set up the path for each record.

You would then check for each platform in the script and either run the applescript or OpenURL depending on the platform.

[HazMatt]

Sounds like the correct way to do it is to use the Open URL script step. (You can do that on the Mac as well.)

My main problem is whether or not my file structure will be predictable. We have a mix of files, including PDF, SolidWorks, Word, Excel, Vellum

[Vaughan]

My main problem is whether or not my file structure will be predictable.

You're going to have to MAKE the structure predictable, and make sure the users stick to the structure otherwise it ain't gonna work!

To some extent it doesn't matter what the structure is as long as it is fixed and rigidly followed. A logical, human-readable system like the one CaptKurt suggested isn't rocket science to develop.

[HazMatt]

ATTACHED FILE: screenshot.gif

Well, I'm finally on my way to implementing this feature (hey, I've been busy!)

I have a reliable folder and file name structure, and our engineers have been informed of the need to keep it that way (very important!)

I will have a button that opens a PDF file based on our part number / revision. Generally, non-engineers will be opening the PDF files.

I also have a feature that opens the enclosing folder of the part files - something that our engineers will appreciate (beats the pants off going through tons of nested folders!)

Here's where my remaining problem lies:

My network drive and volumes are practically always present in Windows. There is no need to "mount" the volumes, like on the Mac. This is good for my file open script, because it is more reliable. On the Mac, however, one must first have the volumes mounted (in this case, "Engineering").

My question is this: is there any way for Applescript to detect if the network volume "Engineering" is present on the desktop? And if not, show a message and / or automatically open Engineering?

I understand the Chooser is not scriptable, sadly. To make matters worse, our Iomega NAS A300u does not reliably keep track of aliases pointing to its shared volumes. For instance, if I have an alias pointing to the Engineering volume, sometimes it works, but most of the times it opens up a different folder or doesn't even work at all.