Store by reference files must be placed in the correct folder on your server before they are accessible to web clients. See the web publishing PDF that comes with your software for specifics.
It's my understanding, however, that FM GO clients cannot see store by reference images in container fields so you may have to not use this option if you want to make them accessible to FM GO users.
Thanks for your reply but I can't say I understand. Why would there be a correct folder? Perhaps my question was misleading.
When I'm using the FM client locally, that is to say on the same network as the Filemaker Server, I can put a file in a designated folder and add a reference to that file in a container field. Usually I use a calculation for this.
Locally, as you would expect, this works well. However, if I start up Filemaker at home I won't be able to see the image that I put in the container field as a reference. This appears to be because the reference is relative to my client and not relative to the Filemaker Server.
Apologies for misreading your original post. My brain turneed "web viewer" into "web browser". That response was specific to Instant Web Publishing.
You are correct that you will not be able to see the images if the filepath stored in the container is not a valid path for the location from which you are accessing the database. Unless you store the files without store by reference, I think you'd need to use a web viewer, but specify a path to the image file that is valid for your user's frame of reference. I would think that this is possible as this can be a calculated expression, but haven't tried it myself so I could easily be wrong here.