I have an Excel macro that imports files into an Access database. The Excel macro uses a shell command to open Access and kick off a macro in the Access database. The Access macro runs an Access VBA function that runs several routines in Access. This works for me. I'm located in the US.
A UK user tries to run the Excel macro. Access opens but displays an error message. The Access database is located on the UK server.
I remoted in to the user's machine and opened the Access database. I then selected "macros" and pushed the "run macro" icon. A pop-up displayed and showed the macro name. You had to click "Ok" or "cancel". I've never seen this before and was wondering if this is the reason that the UK user gets the error message.
Any suggestions would be appreciated. thanks...........
Try going into the settings of his Access. If all fails, download and use this program called Express ClickYes. It automatically clicks yes when message boxes in Access pops up
Related
How can I create a button in form to open attachment window by clicking on it using macros or vba?
Saving objects in database tables uses up Access 2GB size limit. Attachment field is a multi-value type and can be frustrating to manage. Most experienced developers leave files in external folder location. Review Add/view attachments using MS Access VBA and Access Attachment Dialog Window.
However, following code worked for me.
Me.attachmentcontrolname.SetFocus
DoCmd.RunCommand acCmdManageAttachments
We have a single user unable to execute a specific macro in an XLSM file using Excel 2013. The issue seems to be tied to the user's entitlements because he gets the same error even on a freshly imaged machine. I would love to know if anyone has seen this issue before so we can pinpoint what's causing it internally. This can't be replicated by any other user, but is persistent to the user's account on any PC.
When he tries to execute a macro, nothing happens. No error message. Just nothing. On further review, the macro name looks weird in the macros window. It looks like (File Name).xlsm'!(Sheet Name).(Macro Name) instead of just listing the macro name. Screenshot here:
The macro is a public sub sitting on the sheet. If I move the code to a module, the name displays correctly and the macro runs, but that's not the way the code was designed to function. I'm not looking for help with the code. (This isn't mine to change and it works fine for dozens of users.) But I would be extremely grateful if someone familiar with this could give me an idea of what's happening here and perhaps why it could be tied to a user's corporate entitlements.
Thank you!
We have a spreadsheet with some VBA in it that compiles data from multiple tabs to generate a score and pull over comments.
I am the only user who cannot run the macro. When I try to run the macro, either via the macro button or directly from the macro window, nothing happens. This issue is specific to this single file, as I'm working all the time with macro-enabled workbooks. So the problem isn't tied to my Trust Center settings.
My only smoking gun is that most of the code sits in the "ThisWorkbook" Excel Object. If I try to move some of the code to a module, then I can run it, although I get an error since the code was designed to sit in ThisWorkbook.
Any idea why I would be the only person who can't run this macro? Also, I've disabled all add-ins, so I don't think that's the issue.
My team stores their EOM reports on SharePoint. The macro to pull all the files and compile them is complete. The only pain is that when every workbook opens there is a pop up box that says "You are opening from an untrusted source, are you sure you want to open?" I want My VBA code to automatically hit ok or ignore this so I don't have to hit OK for each team member (There are 17). I know I can add it as a trusted source, but sometimes others will need to run this report from their laptop. Suggestions?
I've written an Excel addin that periodically checks a remote repository for data updates, including a check when the addin loads at Excel start up (during the addin's Workbook_Open event). If new respository data is detected, the addin asks the user for permission to proceed with the update. If the user clicks "yes", the addin successfully updates itself and everything is happy... except...
If Excel is not already running and the user selects an Excel file to open (e.g. via double-click in Windows), this sequence of events occurs and everything works, but the user-requested file opening is interrupted and not re-engaged. The Excel app is running, but with no workbook loaded (the workbook area is an empty frame).
I believe I have two options, neither of which I know how to accomplish:
Prevent the addin from completing its update check until the user-selected file has completed its open sequence and is fully loaded, or
Allow the addin to update itself and then somehow re-engage the user-selected file to complete the file open/load.
I have not been able to discover the filename/path of the user-requested file, so my addin isn't able to direct that file to be loaded.
My current workaround is a MsgBox telling the user to close Excel and re-open the selected file. Ideally, the addin update should occur and the original action should complete without requiring user intervention.
(Building on Option 1, I could start a delay timer for the addin to check for updates XX number of seconds after Excel starts, but this seems kludgy to me.)
Any guidance or ideas are appreciated. My interwebz searches aren't hitting the right combination of keywords for the exact scenario.
Instead of opening the new addin update file immediately you can use OnTime to delay it which should allow the other file to open successfully. See here: Process for updating Excel add-in?
In the answer you'll also see a reference to this package here which does everything you need. Autoupdates are hard so I would recommend going with someone else's solution.
http://www.decisionmodels.com/downloads.htm#addload
(Scroll down to Add-In Loader Version 2)