C:\Windows\System32\config\systemprofile\Desktop
C:\Windows\SysWOW64\config\systemprofile\Desktop
This was the fix. I forgot to check the the SysWOW64 account.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Having problem running batch file that triggers access macro to create word documents. The steps and issues
I have gone to Event Viewer but I can not finding anything. There is nothing in the Microsoft Office Alerts. I am at a lost. My initial thought was that the account login for 365 was popping up so I purchased 2019 but it still occurs. Any ideas how to debug this problem?
C:\Windows\System32\config\systemprofile\Desktop
C:\Windows\SysWOW64\config\systemprofile\Desktop
This was the fix. I forgot to check the the SysWOW64 account.
The account you're running under is a normal user account? That user account has a current license for Office? Your batch file is not relying on anything that might be tied to your profile loading like a mapped drive?
Change your batch file to start notepad instead. Does it work? If it does then this eliminates most issues with running batch files under your profile.
Change your batch file to simply start Word. Does it work? If not then the issue is likely the need for a license agreement approval by the account running Office. Ensure the Hidden
option is not set so you can see the UI pop up.
The batch file runs fine. It starts the Access Marco and will complete as long as I am not opening Word. I just noticed that if I change the task to Run only when user is logged in then it runs fine as well.
It has something to do with Word and the user account. Not sure where to see the error or the prompt created. Hope this helps.
Yes, I am opening it through VBA Module in Access. I do not see any permission errors in the Event Viewer. How do I determine this?
C:\Windows\System32\config\systemprofile\Desktop
By the way... I did add the folder above thinking this was the issue but no luck thus far. Thanks again for your help.