User Profile
Villi_B
Copper Contributor
Joined 4 years ago
User Widgets
Recent Discussions
Re: Word Blocked Macros
Check how you open the document from Access: as per Doug's answer to me on Sept 12 at 12:46 AM, my issue came from using createobject() instead of trying first with getobject(), which intercepts the eventual Word.Application instance already open (it works if a doc is open), and then resuming to createobject() if the getobject() fails. That solved my issue which happened only when I already had an open file in Word11KViews0likes0CommentsRe: Word Blocked Macros
Doug_Robbins_Word_MVP This happens on my PC with Office Professional Plus 2016 with Word documents, also I'm almost sure it happens with another version too. The update history says the last one was 16.0.15330.20196 released in June. Word is 2016 MSO (Bersion 2208 build 16.0.15601.20078) 32 bit. The thing which is confusing us is that the issue appears only on the second and subsequent documents. I checked if the file it says comes from a non trusted location already exists but no, it gest created when I try to open the second document from Visual Foxpro code via obyWord=CREATEOBJECT("WORD.APPLICATION","") obyWord.VISIBLE=.T. obyWord.APPLICATION.WINDOWSTATE=1 obyWord.Documents.Open(pathToDocFile, True, True) because if I try to open another macro-enalbed doc file with a double click in Windows Explorer I don't get the dialog telling me the macros are being disabled. pathToDocFile points to a file in a folder I added to the Trusted Paths (I'm translating from the italian version) in Office And it doesn' happen on every PC11KViews0likes6CommentsRe: Word Blocked Macros
I'm in the same situation, our customers started having the same issue during the month of August. I read that the block had been activated at the end of July. The strange thing is that the first document they open (Word doc with macros) opens flawlessly but the second and following ones get the dialog box about the macros being disabled (with the only option to disable them). The path and file name structure of the non-trusted component is exactly the one you are talking about. This is drving us nuts...11KViews0likes8Comments
Recent Blog Articles
No content to show