🚀 go-pugleaf

Ana--

I think that Johannes and Roberto are on the right track (sorry about the documentation Jens--the XMP scripting was not working well when the Scripting Guide had to be completed for InDesign 2.0)--use the label property of some object to store your data.

Roberto suggests adding the data to an object, then training your users to select the object and use the Script Label palette to view/edit the string; Johannes suggests storing the data in the Document.Label and creating your own user interface for it.

Both methods have advantages and disadvantages. Roberto's approach requires that you create an object in the document that users must then select, but has the advantage of using the Script Label palette; Johannes' approach stores the data invisibly and allows for multiple data fields, but requires a separate .exe for getting at the data.

I'd say it depends on the amount of data you want to store/edit. If it's just a single line of text, then Roberto's approach is probably better; if you need to store more information (and multiple fields/records), then Johannes' approach is better.

Thanks,

Ole