Hi, I was able to link to my Dynamics 365 tables with the version 1708 (build 8431.2107) but not with the version 1711 (build 8730.2165).
So I did a rollback to version 1708 and stopped the auto updates.
When will be again available the Dynamics 365 connection?
there may have been an issue with this Office version preventing you from seeing the Dynamics connector.
I can assure you we haven’t removed it.
Please update to the latest version.
With the last version update of Access, the forms no longer scroll. The wheel on the mouse doesnt scroll anymore. The scroll bar also doesnt work when you drag it up or down. Is there a timeline for a fix on this bug? If no known timeline, I will have to downgrade my version of Access to fix the problem.36 votes
Marked as done since this should now be working for everyone.
Already provided evidence to microsoft support; however, I was instructed to post here. Error easily and consistently recreated. Recent Build 1711 fails every time when creating a new table and then simply changing data type to number of large number. 1711 is unstable.1 vote
scrolling with the mousewheel and with moving the progress bar does not work since the newest automatic update - version access 16.0.8326.2073!!!
FIX THIS BUG PLEASE ASAP!!!17 votes
The issue is now fixed in Version 1709 (8528.2139). To get the update immediately, open any Office 2016 app and choose File > Account > Update Options > Update Now.
I am trying to access the training videos for Access at the link below but I can only get the first video to play. Videos 2, 3, 4, and 5 won't play. I chatted with a Microsoft representative and she saw the same issue and directed me to this board. I tried using Chrome, Microsoft Edge, and Firefox but none of them would play the other videos.3 votes
Please try this link (as suggested in the answers thread you provided) – https://support.office.com/en-us/article/Access-2013-videos-and-tutorials-a4bd10ea-d5f4-40c5-8b37-d254561f8bce?ui=en-US&rs=en-US&ad=US
After the latest update to Office 365, we can no longer use the Windows common control C:\Windows\SysWow64\MSCOMCTL.OCX). When opening an Access 2016 database that uses that Common control, it now says that you don't have the license needed to use this ActiveX control, and only blank forms are shown.
This common control has worked for decades in office 2007, 2010 and 2016 up until now.
The version is 1707 (8323.2962).4 votes
This is fixed in build 16.0.8326.2087, which is now available. It will start updating automatically next week, but you can use ‘Update Now’ to get the update now.
make it easy for us to suggest new features for future Access versions: add an uservoice button!1 vote
Please note that in File—>Feedback, Office products have a new button called “I Have A Suggestion”.
It will direct you immediately to Access UserVoice.
Pressing CTRL+A should select all text in a query's SQL View. It does not work in Access 2013.
My current work-around is an AutoHotkey script.14 votes
This is fixed in version 1707 (so in Current Channel, and Semi-Annual Channel (Targeted) now, and will be in Semi-Annual Channel in January 2018).
Note that this only covers being able to use Ctrl+A in query SQL view, so if you have specific requests for other improvements please open a new item.
Access files cannot connect to a .dbf file if the .dbf's file's name is over 8 characters. I am grateful for bringing back support for .dbf files, but these are often created by other applications and we do not have control over their name length.
This is posted following Tisky Zheng's comment in my Microsoft community question here https://answers.microsoft.com/en-us/msoffice/forum/msofficeaccess-msoother/connect-access-2016-to-dbf-file-with-a-name-over-8/b85202d6-e9f2-4489-bb54-45c85a386ea315 votes
A change that supports connecting to dBase files with longer than 8 char names, is now rolling out to O365 customers.
Charts: make the charting function in access as good as excel11 votes
New and modern chart types are now available to O365 customers.
Read more about them here https://techcommunity.microsoft.com/t5/Access-Blog/Introducing-new-and-modern-chart-types/ba-p/193479
Happing a lot in Office build 1611 for no apparent reason, completely stable in build 160946 votes
I host my Access tables on Sharepoint and use Access 2016 as my front-end. I assume this means I use Access Web Services on Sharepoint? I've just randomly come across an article that says this service will be discontinued on Office 365 by April 2018, starting June 2017. Does this mean I will have access to my online tables until April 2018 ? I've contacted Office365 support to find out if I will still be able to synch my tables after April 2018, but they could provide no further information other than the article. I don't see why Office365 should discontinue a service that works perfectly fine and is supported by Sharepoint 2016 ? Please clarify
I host my Access tables on Sharepoint and use Access 2016 as my front-end. I assume this means I use Access Web Services on Sharepoint? I've just randomly come across an article that says this service will be discontinued on Office 365 by April 2018, starting June 2017. Does this mean I will have access to my online tables until April 2018 ? I've contacted Office365 support to find out if I will still be able to synch my tables after April 2018, but they could provide no further information other than the article. I don't see why Office365 should…4 votes
I am new to using Access. I would really like an easy tutorial. A beginner tutorial link would be nice.1 vote
A simple Bing search would yield additional resources.
Microsoft Power App Instructions -- need detail in the form of published books1 vote
Please visit the PowerApps community to ask PowerApps related questions and suggest ideas:
The Access Team
We recently updated our desktop Office programs from 2007 to 2016 Professional Plus. I just went to open a database and run several queries and got an ISAM error. When searching the web I found the post from here about MS bringing back support for connecting to dBASE in Office 365 only. First, it made no sense to remove it and second, why would MS only bring it back for 365? Why would MS remove this capability in the first place? Has MS committed to bringing it back and, if so, when will it be available? I now have to uninstall the latest version and install 2010. Please bring this feature back for the desktop 2016 version of Access. Are there any other things that MS arbitrarily removed from this or prior versions?
We recently updated our desktop Office programs from 2007 to 2016 Professional Plus. I just went to open a database and run several queries and got an ISAM error. When searching the web I found the post from here about MS bringing back support for connecting to dBASE in Office 365 only. First, it made no sense to remove it and second, why would MS only bring it back for 365? Why would MS remove this capability in the first place? Has MS committed to bringing it back and, if so, when will it be available? I now have to…9 votes
Please note that to enable dBase, customers will need patches for both Access and ACE:
This would be more restful the eyes than the glare of the white or "colourful" settings used at present.4 votes
Dark and black themes are available to O365 subscribers starting version 18.11 (11029.20079)
Make the borders larger around tables in query design view. Was easier to change the size of tables seen in design view in earlier versions
Increase the width of borders around the tables seen in query design view. Earlier versions of Access (2007, 2003) had wider borders around the tables in query design view and it was easier to change the size of the table. Clicking and dragging the border to change the size of the table is much easier when the border is wider because the mouse pointer doesn't have to be in such a precise location.3 votes
I support an application with over 90K registered users for a international logistics company (the guys with the brown trucks). We can not support the 64 bit version of Office Access because there is no 64 bit version of this library. Converting the Tree Views to use .Net would be cost prohibitive.24 votes
There is a spelling error in Microsoft Access Expression Builder. It is in the descriptions of DLast and DFirst. It reads "Return a random record from a particualr field in a table or query when you simply need any value from that field." The word particular is spelt wrong in your description of DLast and DFirst.1 vote
Thanks for reporting this.
- Don't see your idea?