Join Gini von Courter for an in-depth discussion in this video Introduction to Access web apps, part of Creating Access Web Apps in SharePoint 2013.
- This is an Access web app. It's is the Access web app that we're going to create in this course and it's something can be created in a matter of hours rather than a matter of days or weeks and it runs in a browser. It's hosted in SharePoint. We have tables. Those tables have relationships. Users can add new items to tables. They can delete items. Edit items if they wish. We have different views, datasheet views, and list views. And we have the ability to add code or macros so we can do some pretty remarkable things like create a filter that finds the open issues that are due in the next 30 days.
Or reports that there aren't any. We navigation that's just beautiful and the ability to look at comments or related issues for different issues that we're examining. We can look at any of the tables so we can look at an employee for example and find any items that were opened by that person or issues that were assigned to them and the background that we see is actually based on the site because this is running inside of SharePoint.
This is part of the KinetEco team site. So, if I say I wanna go back to the site I'm simply leaving this particular app and returning to KinetEco. For those of you who are SharePoint focused if we go take a look at the site contents what you'll find is that this app called Issues lives right here inside of SharePoint. So, what is an Access web app? Access web apps allow you to collaborate with your team or organization with your data securely on the web in a browser.
Apps can be simple like the app I just showed you or incredibly complex. You can jump start your app creation process by using templates. That's what we're going to do. Or you can create totally custom apps building every single table from scratch or importing data from tables that you have already. So, if you imagine that you have a data table that you want to share and have many people be able to work with it and be able to view it one way you can do that is in a SharePoint list. But another way you can do that would be to take that same data from Excel or wherever it's stored now, perhaps even a in a SharePoint list, import it into Access and create a web app that would allow all of your users to work with that data in an environment that's relatively easy to create and easy to maintain.
Access web apps are brand new for Access 2013. They're Access applications that are hosted in Microsoft SharePoint either on premises or in SharePoint online or SharePoint for Office 365. You're going to design these using the tools that you have in Access. So, this is my design environment. I can work with tables and edit them. If you're an Access person, that should look familiar. And I can also edit the forms which are called Views.
I also have the ability, if I wish, to add queries and to add macros. And, of course, when I'm done my product runs in a browser. That means that I don't need to ensure that anyone has access to Microsoft Access. Many organizations only put Access on some desktops rather than all and if you're thinking, "I'd like to do some development in Access "but not everybody has it." They don't need to. As long as they have SharePoint and you have Access 2013.
This is a step up from the last version. In Access 2010 we had web databases and they stored their data in SharePoint lists. They ran on Access Services 2010. Web apps on the other hand are created and designed in Access 2013. They're data is stored in SQL server and in the newest version of SQL server you can't use SQL 2008. You need to use SQL 2013. And run Access Services 2013.
What that means if that if you have a web database you really can't simply upgrade it. There's not a migration path for that. So, if right now you are working in the environment that you see on your right where you have Access 2013 available to you. You have SQL server 2012, you have SharePoint online or SharePoint on premises running Access Services 2013 there's no reason that you would develop a web database. Because web apps, not web databases, are the future.
They create up browser-based applications that are simple and easy to use. Who wouldn't love this? If you were an Access developer in the past, particularly if you haven't done this in a while, and you're wondering, "Is there something in this for me?" This is different than anything you've seen before in Microsoft Access. And if you're primarily a SharePoint power user and you're wondering, "Is there something "that I might wanna learn here?" If you have data you want to share I would like to encourage you to take a look at what you can do with Microsoft Access 2013 web apps for SharePoint.
Let's get going.
- Creating a new app
- Building tables from different sources
- Creating relationships between tables
- Working with views
- Using macros for automation
- Saving your app in an app package
Skill Level Intermediate
Q: The "Using the If macro action" movie seems to end in the middle of troubleshooting. What am I missing?
<div>A: You’re right—and a replacement movie is on the way. In the meantime, here is the solution:</div><div> </div><div>The IssuesNext30Days data macro sets a local variable, originally named ApplyFilter, equal to RecordFound. During troubleshooting we change the name of the ApplyFilter variable to TurnOnFilter but the name doesn’t matter. Our problem is that ApplyFilter is a local variable, so it only has value in the IssuesNext30Days macro. We can’t use this variable in the IF condition of our web macro. </div><div> </div><div> We do, however, have a value that we can use: the value of RecordFound. To complete debugging on this macro, change the condition in the web macro to: </div><div> </div><div>If [RecordFound] =”Yes” Then</div><div> </div>