Cross platform container fields as reference?

[mga]

I've got a database of about 400 staff in my organisation. This runs on an Xserve/FM8 server. The database is very simple, with just contact names and a photos.

I wrote the database on a Mac, and asked one of our admin staff to add the staff photos. They're stored in container fields as a reference, not added to the database.

Although this works fine on the Mac, all the references are broken on Windows. I suspect that this is because the path is different. My question is:

1) Is there an easy way to fix the existing file to work on Windows?

2) If not, can I at least get the path out of the container fields somehow, so I can create a calculation field from it with different Mac/Windows paths.

3) Failing all the above, how should I recreate the photo field to work on both platforms?

Note: I have the Troi File plugin if that helps.

[Fenton]

Create a calculation, text result, GetAsText ( the container field ). You will then see the current full path to the container. It likely has the prefix, "imagemac:". You'll need to toggle that prefix, depending on platform:

Case (

Abs ( Get ( SystemPlatform )) = 1;

"imagemac:";

"imagewin:") &

"/full path to image"

[mga]

Thanks. I did what you suggested, and got the result:

size:70,95

image:../../../../../ General graphics files/photos/GONW staff 72 dpi for Intranet/staffPhoto/041126 Anderson_Judith.jpg

imagemac:/XSERVE/ General graphics files/photos/GONW staff 72 dpi for Intranet/staffPhoto/041126 Anderson_Judith.jpg

I can see the information I want in there, but there's a load of other stuff in the way. Are you suggesting I parse it for the filename (everything except "041126 Anderson_Judith.jpg" in the above example is common to all records) or is there an easier way?

[mga]

Actually, it turns out the path isn't always the same; just getting the filename wouldn't be enough. I need the entire string after the word XSERVE.

Any ideas?

What I think I'm going to do is write a script to copy across the picture, but this time store it within the database (ie. not as a reference). This should work on Windows.

Will the accordingly larger file be a problem, given that the database will be running from the server? I mean, the image has to be copied over the network, so it doesn't make much difference if it's from within filemaker or from the Mac filesystem. The bigger database isn't as elegant, but I can't see it being a problem?