Recently, we have had various MS Access 2012 apps become unresponsive to mouse clicks.
This happens in both in either run or design modes for forms, reports, queries, etc.
Usually, when I put the focus on another program by bringing it up and clicking in it, then go back to the Access app - it is then responsive.
Now it is happening to our Citrix users and the trick doesn't always work.
Anyone have any ideas, fixes, solutions?
Related
I have an Access 2000 application that a client wants updated to Office 365. The old db has a toolbar that I’d like to use but it appears under “Add-Ins” on the main ribbon. The toolbar works just fine but it’s very awkward and unprofessional to have the user select it from the add-Ins menu. How do it make visible when the db is opened?
Is this still a mdb, or was it converted to accDB (or accDE)?
How big/extensive is the add-in menu? (extensive, or just a few options???).
If just a few options, then you could create a custom ribbon.
A HUGE but BEYOND huge tip? - don't use ribbon call backs. I can expand on this suggestion. But as a general rule the SAME command for the menu can be created and used for the ribbon - and without a call back.
So, right now, about your only option would be to:
Use an access 2000, or 2003 runtime (if you have a copy).
Or consider building a custom ribbon. I mean, a2000? That is 22 years ago.
When developing my report in BIDS, the Go to Bookmark action is pretty quick but after deploying my report to the server any bookmark click takes about 10 seconds with the "Loading" pop-up. My report is 1 (potentially long) page but it displays a lot of information so i wanted to be able to add a little index at the top. I've tried DocumentMapLabel as well but it's the same loading issue but I have no control over how gargantuan the side bar is for the tiny tree map it displays.
My query runs in less than a second so pretty much all of the time waiting is on SSRS.
Any ideas what is going on or if there are setting i can change to make it more snappy?
thanks.
well, i work remotely so i'm not on the network that the report server is on directly. After remoting into a machine that is, the bookmark feature is nearly instantaneous. I'm not sure why it matters for this feature but I suppose i'll be testing my report on the remote machine instead.
I maintain a campaign scheduling database in MS Access, built from scratch. It's been running for two years with few problems. It has a userbase of around 50 account managers.
This week, there was a Microsoft Office update which has disabled mouse scrolling on ALL forms within the database. As the forms are almost all continuous forms containing campaign scheduling details split into days, weeks and months, being able to scroll through is important. Mouse scrolling has always worked before.
Does anyone have a fix for this?
I built and successfully split an Access 2013 db. The front end worked fine for months up until I last used it a few months ago. I recently went to open the front end but the Access window was frozen whereby everything (e.g., navigation pane, menus, controls, right click, etc.) was disabled, including the window control buttons to minimize, expand and close. The only way to close the view was to right click the Access icon in the task bar or 'ctrl-alt-delete' to open task manager and force close the application. I was met w/ similar results when attempting to open other versions of the linked front end; however, I can successfully open the back end and other Access db files that don't contain linked tables. When I get the 'frozen' screen I can see my linked tables and other db objects in the navigation pane, but the pop-up login form does not display and the entire window behaves like it is inactive, similar to how it behaves when selecting items behind the active login form.
To confuse matters even worse, I have one user (User 1) who has the same user permissions as me who does not experience any of the problems I described above and can work within the front end as expected; in fact, he and I are the only active users as we are still in the developmental phase of our project. One other layer of complexity, he tried to open the file w/ his network profile from my computer and ran into the same problems. We have one other user who we've since tested this problem with and she experiences the same issues as me on both her laptop and PC.
So, I thought maybe it had to do with the 32-bit version I unknowingly had installed when my OS was re-installed last month since User 1 had the 64-bit version which could explain why he couldn't open from my computer. BUT, I still experienced the same issues after re-installing the 64-bit version on my computer. I'm at a loss on where/how to proceed from here and my IT guys have done all they can to troubleshoot my problem as they are not familiar w/ Access and aren't much help at this point.
Anyone run into this problem before? Thoughts or possible solutions? Any and all help would be greatly appreciated, thank you.
So, I disabled the code that prompted the login form and I was able to open the file. Based on User 1's experience, we determined that he hadn't installed updates since I was last able to open the file. As a result, we determined that an update I installed was not compatible w/ the aforementioned code resulting in the problems I described in my original post. I will re-create the code that drives the form's login and keep an uncoded version as back-up in case we experience similar issues in future updates so that we can troubleshoot from within the db rather than be locked out as we were.
Recently, my team's Microsoft Access databases have been migrated from Access 2003 to 2010. Obviously that causes a many problems, but we got most of them figured out. There is one problem, however, that I can't seem to fix.
Many people use this Access application with no issues at all, but about three of my users are experiencing a peculiar problem.
There is a subform within a form and its contents get loaded through a query. There is a box for a picture, a text box, a check box, and a button on this subform. For myself and 99% of the people using the application, the picture loads and everything appears as it should. For the 3 people experiencing the problem, however, the entire subform is completely blank.
The data is stored in OLE Objects and everybody is using the same data.
I can't figure out why it would work for so many people but fail for others. Does anybody have any ideas?