My question is this: Are their any unforeseen problems with designing the application this way -- performance-wise? And how will these objects display and work when viewed with a Web browser vs. a Notes client?
I don't know a way to make the OLE editing work in a Web browser. The embedded object is just rendered as a graphic in HTML. But you can see that image when it is converted to a GIF of JPG (depending on HTTP server settings).
There's a function on attachments, available thru the Notes client UI, that lets the user launch them for editing as opposed to just "opening" them. Any changes are automatically recorded into the document attachment when the document is saved. If users can be trained to use this -- or if you give them an action button that does the same thing -- then attachments are as usable as OLE objects, except you don't get the image when you view the document in read mode. On the plus side, you use less storage since attachments are stored much more compactly.
Dig Deeper on LotusScript
Related Q&A from Andre Guirard
Learn how you can use LotusScript and OLE to create and populate Microsoft Excel spreadsheets, as well as a little bit about Lotus Symphony. Continue Reading
Discover options you can use if you'd like external users to be able to access a workflow-based Notes Domino application through different ... Continue Reading
Learn why you may receive the error message: "Illegal circular use: Audit Trail" when trying to open Lotus Notes documents that use copied forms. Continue Reading