I’m using the “Microsoft Office Library” template that comes with R6, and I’m finding it hard to believe that Iris have made a template that requires a really lax ECL in order to work at all. Is this right or have I missed something?
When creating an OLE object in the front-end (e.g. embedding a Word document) it gets signed with the current user’s certs. Activating that object comes under “Access to external programs”, and so will only work if (a) the creator of that document is listed in the ECL, or (b) -Default- has access to external programs.
I guess that’s fair enough (but looser than I’d like to have my ECL), but if you choose to migrate documents from the file system to the library database, the resulting documents have unsigned OLE objects, so for that to work you need to give -No Signature- access to external programs, which is asking for trouble.
Is this really the situation, or am I missing a trick somewhere? It would be nice to use an OLE-supporting template without throwing the doors wide open. If it was “just” a case of all users in my domain having to trust each other like this, I could just about cope, but if it’s going to end up putting unsigned objects in I’m not happy.
Thanks,
Toby.