🚀 go-pugleaf

Oops, yes the name for the table should match of course. I meant to use "tblMyTable" in both the code and what you name the table... 

As far as running VBA from Access: sure you can do it from a form, but it's also nice to just run it from code (there is almost zero need for macros in Access): to do so you simply click anywhere in the function and press the "Play" button (the triangle on the tool bar). 

Rather than paste a whole gobb of code behind a form event, I find it better to call the Function or Sub from a form, in this case if you had pasted it into a module, the onclick event for the form button could be simply: 
Output 

Glad you got it to work... should lead to some more questions (tried to just give the bare bones DAO context): I've hit many initial obstacles with InDesign scripting when first trying things, but none that couldn't be solved. It is a great program and the best API for scripting that I've ever seen: all the objects you would ever need are exposed. I think the challenge is the object model; you have, for example, so many different ways things can be done and so many sort of overlapping objects: you can get at text from the story, from the textframe, from the paragraph, from the selection. That's probably just due to the nature of page composition, but it can take some getting used to.