We are using a set of files in stand-alone process (migration). This set of files contains (5) files used to process the migration and (5) files which are normally served. We want to run the migration from intermediate data to final solution without being stopped by the 'FileMaker cannot share a file ..." dialog.

I believe the only way is to turn off file sharing on each file separately before the migration (then turn them back on after). But I just wanted to check if there is a way to handle it within a script because it stops the migration from running automatically. I've been clear through the Errors list and can't find anything which might help us. We can remember to turn them off but, the less a person has to remember the better because, not only would they need to remember to turn it off, but they'd have to remember to turn it back on as well. Ideas appreciated.

I guess the best we can do is begin (and end) the process with script-step Open Sharing. I was hoping for full automation but I can be overly fussy.

I presume your trying to stop the local files interacting with the served files.

If you set the file paths correct in the "local" solution to use only the "local" files, and the file paths in the "server" solution to use only the "server" files then you can run FMP with file sharing ON as you will effectively be running 2 solutions at the same time.

HTH

Thank you, Mark! Files are unserved for migration. On one local migration file, it was set to 'all users' even though networking was set to OFF. As soon as I corrected that, the message stopped.

So we can leave sharing ON for our networked target set and just be sure it is set to OFF on all migration files (we must ALSO be sure it is set to 'no users' even if set to OFF or it will fail). And, since the target files aren't opened during the process, the message will be suppressed.

This will prevent many irritating moments because I confess that the network sharing message is a PIB to me. I hope I have the principle correct. :wink2: