inserting a picture is a record edit and that requires write privileges, no way around that.
Putting the file on a shared folder will very likely generate user conflicts (multiple users trying to open the file and write to it at the same time). FileMaker Server is the only good way out of this.
sorry, I should have written 'the picture is located on a file server'. The (FileMaker) file is located in a place that has write priviliges. So it's the fact that the picture has only read priviliges is giving FileMaker Pro to generate an error code is what is quite strange.
best regards - Dick