Portland Access User Group

Portland Access User Group Conference

September 28-30, 2019

The PAUG Database Designer International conference brings together a wide range of Access developers, consultants, power users and Access enthusiasts. This marks the 21st anniversary of the conference. We will once again be returning to the peaceful and natural surroundings of the Conference Center at Silver Falls State Park, which lends itself to a climate that fosters learning, creativity, and socializing.

Sunday, April 2, 2017

Access 2010 Web Databases: How Can I Put My Access Database On The Web?


Unfortunately, as of Access 2019, Access Web Apps have been discontinued.  From the March 2017 announcement from Microsoft:
“We no longer recommend Access Services for new apps. This feature will be retired from Office 365. We will stop creation of new Access-based apps in SharePoint Online starting June 2017 and shut down any remaining apps by April 2018.”

How Can I Put My Access Database On The Web?

One of the perennial questions in the Access newsgroups and web forums is "How can I put my Access database up on the web?" Until recently, the only answer was "Learn ASP.NET or PHP and re-program it."

With Access 2007, it became possible to upload your data to a SharePoint list in the "cloud", that is, a server somewhere up on the web. However, the actual application still had to be run in the Access client, either in Access itself or the
Access Runtime.

But with Access 2010 and Access Services in SharePoint 2010, it is possible to also publish your application, (ie, forms, reports, queries, and macros) up to the web as well as the data. From there, the application itself can be run in a browser. So the new answer is: "Go to the File menu, choose 'Save and Publish' and then 'Publish to Access Services'."

Can it really be that simple? Well, no. Not really. The chances that an existing application of yours will simply upload to the web are relatively small. SharePoint Access Services has specific requirements both for your data and application design. Some of these requirements may be at odds with your existing development paradigm.

For instance, a SharePoint back-end does not have relationships per se, it cannot have a composite primary key, and cannot have multiple field indexes. Web database applications cannot have any VBA code, only macros (although the new macros in Access 2010 are more robust than previous versions), and forms must be designed in Layout View rather than Design View. This is not an exhaustive list, just a few examples. I'll discuss them in future posts where I can go into more depth (and as I discover them).

Of course, I needed a project to use, so I decided to take an existing application and make it a web application. I have a sample on my website (
Books.mdb) which is fairly simple (just a home book inventory database) but also has all the elements of a robust application. As an application, it's not horribly complex, but it should be enough to give me a good workout. If you're interested, you can download the sample and see what I'm up against.

One last thing before I get started. If I am to create a web database application, I need a server running SharePoint 2010 with Access Services. Hosting services for the samples on this blog are provided free of charge by
accesshosting.com.

So let's get started.

The place to start (as with any database application) is with the data. That's what I'll do next time in
Access 2010 Web Databases:Web Compatibility.
.

No comments: