In Instrumenting co-operating app I showed how a web app might create some data in a dead drop to pass back to VBA. In my example, i happen to deal with messages using a log, as described in The dead drop log, but that's not mandatory. All you need is some way of knowing which dead Drop class instances you are expecting to hear from.
Note that there is no specific structure to the message - it's something that you define. Here's what I got back
Using this code
When I first created this data in getting a deadDrop handle from VBA, i created a data field called subject that would contain the worksheet for which this data is destined. So the first job is to find that in the returned data. Once I have it I can load the original sheet.
Now I can get associate the data through the uniqueid field, and update the comments column
and delete the original message if I want (note that the subject line is still there - i could have deleted that too, but leaving it will mean that additional data can still be entered until the message expires)
with updates collected from the web app and picked up back in VBA
Services > Desktop Liberation - the definitive resource for Google Apps Script and Microsoft Office automation > Things that have been deprecated > Google Apps ScriptDB > ScriptDB as a dead drop >