You need to map/mount the remove server's drive or a shared directory on that drive. This makes the location "look" to your computer like you added another drive to it and you set up your path to point to it just like a file on a local drive.
The simplest way to get the path right, is to put the file in that directory on the remote server and then insert it into your container with the "store a reference" options specified. It's possible to use a script that loops through a batch of records to export container field contents to a new location and to then re-insert them with the "store a reference" option specified to do a "batch update" of your container field data.
This requires that each user map/mount the drive or shared directory in exactly the same way and this is why FileMaker 12 adds and external storage option as an alternative that avoids this issue.
Thanks Phil. I wondered about something like that, but I couldn't figure out how to map a drive to the remote server.
Which, I realise, makes this a Windows problem and not a Filemaker problem. However if anyone knows how to map a drive letter to an IP address, I'd love to know.
I don't know why I can't just map a drive to //xxx.xxx.xxx.xxx/covers/
But Windows is unhappy about it.
Alternatively can anyone think of how to improve the printing of the webviewer? Or is there some, third way that I haven't thought of to store references to the images?
This is an OS issue.
On Windows XP
Open My Network Places
Select "Map Network Drive" from the Tools menu
Click the browse button, then find and select the drive or directory that you want to map to a new drive letter for your computer.
I imagine that the steps are similar for other recent versions of Windows.
I believe this is a image issue and not a web viewer issue. I believe that your images are at a low resolution (Under 100dpi, which will look find on your monitor). Most images to look good on printouts need to be 300dpi to 600dpi. I would try using 300dpi because the higher the resolution the longer it takes to load and print. You may have to use imaging software to change the resolution.
Phil - that's pretty much what I was trying to do, but I can't persuade Windows (XP or 7) to accept the IP address. I can navigate to existing drives but I can't navigate to a directory on the internet. If I had a home network, or if I were in one of the offices, I'm sure I could navigate to a network drive, but the offices don't run on a common network. Of course, we could just have a directory of images on all the networks, but it seems kinda inefficient and would raise synchronisation issues.
It looks as if this may be a feature that exists on FM12, but we're not going for that at the moment because of the break in the file format. We have too many users and several databases on the fp7 format and don't want to have to buy a load of new licenses.
s. Chamblee - I think you're probably right about the image resolution. I'm not sure, off the top of my head, what the resolution actually is and I'm no expert in imaging software. The Oxford crew have gone home now for the day, but I'll get someone there to look at this for me tomorrow or next week.
Many thanks to both of you for the suggestions.
Yes, this won't work if you can't map the drive, you'll need to use the web viewer or set up something like VPN so that you can map it.
That's what I was thinking, Phil, but I just wanted to check I wasn't missing anything.
I'll get someone to look into the image resolutions when they open up again in Oxford tomorrow. Maybe we can rejig them to print better.
I have a VPN connection to one of the US offices but not to any of the others, but it's a definite possibilty.
Thanks, once again.