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?
Related
A couple of weeks ago, our Access application suddenly began to fail mysteriously. Comboboxes on random forms would not fill with rows when recordsources were set. These include forms that have not changed in years. Stepping through the code in the debugger always results in a successful outcome. Trying multiple times consecutively would occasionally work. One or two computers still work reliably, though these have a source control addon called Ivercy installed. When you run the deployed version (without the addon active) these machines show the same unreliability.
Last week, we found more issues including some forms and reports that would not populate on initial opening. Reselecting the same filter date (or other rowsource changes) once the form is open brings up the expected set of rows. Again, loading the form while stepping through the code always works.
These behaviours lead me to believe there is some sort of fault that has been introduced in a recent Access update. Has anyone else seen this kind of problem?
One instance of this issue occurs on a very simple, one page report that has no user code in it at all. I would have been willing to believe that we had been doing something systematically wrong in our code, but this code-less report seems to suggest otherwise.
My machine (which exhibits the problem) is using Microsoft 365 Apps for enterprise
Version 2105 (Build 14026.20308 Click-to-Run)
For some reason our SSRS schedules appear to have stopped running over the weekend.
I checked the schedules on our SSRS portal, these appear to have disappeared "There are no items to show in this view". I get the same under my subscriptions, too.
The agent jobs appear to be running, but not emailing reports. When I check the Subscriptions on SSMS, it has run dates for today but no emails.
I have sysadmin and full rights to the server and the SSRS portal.
Anyone come across this issue? I've been searching google all morning to no avail.
Thanks,
Russ
Resolved
Our SSRS dba had only place schedules onto reports locally - you can see this by clicking on the drop down arrow of the report, selecting manage, and then subscriptions from there.
The reason our reports weren't sending is because there was mail delivery had been suspended whilst IT carried out maintenance.
Thanks for your help in trying to get to the bottom of 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?
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?