In the application that I look after, I have some container fields. Until now, these fields have stored file references only, meaning that the user can double-click on the file reference to open the file. They can then edit the file, and save it again.
Because of issues with shared folders, I'm now considering switching to storing the file itself in the container field, using Managed Storage. But as far as I can see, this will not allow the user to open the file in situ - they'll have to export the file contents, edit and save it, then re-insert. I can make the export easy for them by scripting it, but it seems to me that there will inevitably be issues with the new version of the file, with users failing to re-insert, etc.
Or am I missing something? What I really need to do is mimic the current behaviour, i.e. user opens the file from within the application, and the edited version gets automatically saved back to the Managed Storage folder.
Any suggestions much appreciated,