A couple of questions to clarify your situation, and some general observations:
- You talk of local and network accounts. Are these files being served by FM Server or by a Peer-to-peer client-based sharing? Or are you meaning the difference between LAN and WAN access to FM Server-served files? If you are not using FileMaker Serve to serve the files, you should correct that.
- Time Machine or any otehr backup utility should not be allowed to touch served files. This will cause problems whether you are sharing via Peer-to-peer or on a Mac Server machine. It can even corrupt the files. Use FM Server's built-in backup scheduling to backup the served files, and don't let Time Machine (backup utilities) touch the actual served files. If properly configured, you could have Time Machine (or other backup utiltiy) backup the backup files, but not the original served files, whcih need to be excluded from any backup software.
it's basicall an article database where the users can put images to the article.
The images comes from professional photgraphers, e-mail or web. Normally the users have the images on their desktop or o a file server.
In the applicationa I just store the reference of the image into a container with normal Filemaker script "import image (as reference)".
After that the image is copied to the filesystem (in different resolution an a thumb is imported into the database) and the filepath is stored in th database.
But already the first step "import image (as reference)" gets the error back, that the file is in use by an other application.
This script runs since years and never got problems.
The problem only occures on Lion Macs with nethwork accounts (the user account is stored on the server).
You cannot store a container item as a reference only if it's source is a local disk, if it needs to be available to all users. You need to actually place the container object file, not a reference-only, into the field so it will be available to users who do not have read access to each other's hard drives for a reference to resolve.
Even if they all had read access to each other's drives, resolving all the references across all the network from multiple drives would grind things to a halt. And FM Server cannot itself read items from drives to which it does not have full server permissions.
So don't use the reference only option on a network unless the container-content files are are located in a directory to which FM Server has full access on its own system.