Forum Discussion
Microsoft Access Version Comparison Matrix
- Jun 08, 2018Hi Colleen,
Let's address this piece by piece. Access wasn't part of Office until Access 95. Please see this Wikipedia page for details on the history of Microsoft Office. https://en.m.wikipedia.org/wiki/History_of_Microsoft_Office
I undrstand the issue of file names in 8.3 format with dBase and Paradox, but what does that have to do with Access? It's reports are inside the Access mdb file and not subject to 8.3 limitations. You can name a report with much more flexibility.
For "Access Services", do you mean Access Web Services? The latter is deprecated on Office365, but remains supported in on premise SharePoint for the current and next release. Those Apps were never comparable to Windows based versions of Access solutions.
Access has been my choice for data management for years, but I now have clients with limited/non-existent in-house tech support, and the need to enable external users and virtual teams to view/edit data. SharePoint Online and Access Web Services would be the ideal solution.
I don't want Access to be able to consume SharePoint lists. I want to build data tools in Access and publish to SharePoint Online, converting Access tables to SharePoint lists. There are some limitations that constrain the design process, but still easier than building relationships between SP lists natively.
Unfortunately, Access Web Services have been deprecated from O365. On-premises Sharepoint sites will continue to support AWS through at least the next version, but who knows what will happen after that.
"I don't want Access to be able to consume SharePoint lists. I want to build data tools in Access and publish to SharePoint Online, converting Access tables to SharePoint lists. "
Aren't those one and the same thing conceptually? Once you have created tables and exported to SharePoint, you then link back and consume those lists as linked Access tables.