Tag Archives: access web database

Working Offline with Microsoft Access online database

Becoming comfortable with working offline and syncing to an online database with SharePoint later is essential if you often travel or work in areas with intermittent Internet access. Newer versions of Microsoft Access make this transition nearly seamless and help you avoid losing any work. However, there are a few tips that you should know that will allow you to tweak how Microsoft Access works with any website database.

Before you begin using Microsoft Access, you should be aware of two common hazards of working offline. First, if you share a database with coworkers, they may accidentally make conflicting edits when you’re working on a database. When working online, you can recognize these conflicts almost instantly, but you may generate multiple record conflicts when working offline that will create additional work and double-checking. Second, synchronizing with an online database can time out, so you may have to limit the amount of records you edit at one time. The solution to both of these potential issues is to sync offline work with the online database on a regular basis.

Offline Mode with MS Access 2013 and 2010

Since the 2010 edition, Microsoft Access web database automatically places you in offline mode when the computer is not connected to the Internet. Please note that you’re still restricted to online-use only if you’re using the 2013 Microsoft Access web app.  Unfortunately, the offline functionality of Access 2013 Web Apps is non-existent.  If you are disconnected, your frontend reports and forms will stop working/rendering.  The 2013 Web App acts very similarly to connecting your backend data via ODBC or SQL – if that connection isn’t live, you can’t edit or access the data.

The Microsoft Access web database saves any table changes locally using a jet table. The program indicates offline mode with a status bar at the bottom of the screen. Then when you reconnect to the Internet, Microsoft Access will immediately try to reconnect with SharePoint 2010. If Microsoft Access is successful in connecting with the server, you will see a yellow box that asks if you want to send your changes to the server, close open objects and synchronize with the server. If you want to upload your changes to the server, click on the “Synchronize” button.

If you do not see this prompt, go to the “File” menu and choose the “Reconnect All Tables” option.

If you prefer to work offline, bypass online mode in Microsoft Access by clicking on the “External Data” tab. Select the “Web Linked Lists” group and click the “Work Offline” option.

To resume working online, navigate back to the “Web Linked Lists” group. Then click on the “Work Online” option, which will be exactly where the “Work Offline” option appeared before.

To sync database changes, select the “Synchronize” command in the “Web Linked Lists” group on the “External Data” tab.

To discard database changes, select the “Discard changes” command instead.

Working with MS Access 2007 or Earlier

Older versions of Microsoft Access do not have the automatic offline mode. Instead, you should specify when you want to work offline on a SharePoint database, and Microsoft Access will use XML caching to save your work. When working in areas with an intermittent Internet connection, consider working in offline mode and regularly syncing your work to avoid losing any data. Another option is to use one of Access Hosting’s Remote Desktop clients to protect your work and automatically backup your files to any cloud-based storage service when online.

To work offline, open the database on SharePoint and click the “Work Offline” option located on the External Data tab.

To resume working online, go back to the “External Data” tab and select the “Work Online” option.

To update the database with your work and see any changes made by coworkers, select the “Synchronize” option on the “External Data” tab.

If you prefer the greater control of the earlier XML caching, you can turn off the caching in the Microsoft Access 2010 and 2013 versions by navigating to “Access Options,” selecting “Current Database” on the left side and unchecking the box next to the option that says, “Use the cache format that is compatible with Microsoft Access 2010 and later.”

Posted in Access 2007, Access 2010, Access 2013 | Tagged , , | Leave a comment

What is the differences between Access Hosting’s SharePoint and Office 365

I was recently having a very good chat with a potential customer that had some very good questions regarding Access and Office 365.  This person already had an Access app and was looking to share it online in the browser and was thinking that SharePoint was the best solution but was confused about what they needed exactly since they had an Office 365 plan with a few users with just email and a few more with Sharepoint and more.  It was such a good conversation that I thought it would be good to clarify some of the differences between Office 365 and our SharePoint 2013 Enterprise hosting plan for Access Web Databases and Web apps.

Cost Savings over Office 365

The most confusing part of the comparison is that the varying plans for Office 365 are quite confusing in and of themselves.  Office 365 is a sort of all encompassing term used to describe a lot of different products from Microsoft.  It can be as simple as a subscription to Microsoft Office software or a complicated enterprise plan with access to Exchange, Sharepoint, Yammer, and more.  If you’re interested in Access Web Databases or 2013 Web Apps, the first thing to determine is whether your Office 365 plan even includes SharePoint Enterprise.  You need to have either an Office 365 Business Premium plan ($12.50-$15 per user per month) or an Office 365 Enterprise Plan ($20 per user per month) to have access to the correct version of SharePoint with Access Services.  Obviously if you have a small business where you have 10 users or less and need email, exchange and everything in between, Office 365 is the better deal, but for a lot of people they need something more flexible.

Let’s say you have Office 365 and are paying $15-$20 per user and have an Access database that you want to host in SharePoint as a web app and share with some of your clients outside of your organization.  How do you do that if they don’t have their own Microsoft account/Office 365 account?  Our $99 SharePoint hosting plan has been tailor made for Access Services 2013 and 2010 and offers substantial cost savings over Office 365.  Right off the bat our $99 plan includes 10 users ($50 – $100 less than Office 365), and each additional user is only $3 per user per month vs. the $15-$20 per user Office 365 plans.  Best of all, you don’t need to pay for all the extra features of Office 365 that you don’t need for you and your clients.

Access Services 2013 and 2010 running Side by Side

Another cool feature about our $99 Sharepoint plan is that you can run 2013 Access Web Apps right alongside Access 2010 Web Databases since our 2013 SharePoint environment is running both versions of Access services.  We’ve already written about the differences of this technology in a previous post: picking between Access 2013 Web Apps and Access 2010 Web Databases.

Comparing Access Hosting to Office 365

Here’s a few more points about our implementation of SharePoint over Microsoft Office 365. An On Premise or 3rd Party Hosted Access Services 2013 implementation helps provide focused, reliable solutions for the following common customer needs:

  1. Web Based Reports: SQL Server Reporting Services can be used to create reports and link them back into the menu structure of the web app. Access 2013 web databases use the browser as the primary interface to the client. This environment provides an excellent cross platform solution that allows users to participate without a copy of Access on their desktop and create/read/update/delete records in the database, but it lacks a mechanism for reporting on that data. With SQL Server Reporting Services (SSRS) you have the ability to deliver browser based reports to your users alongside the Access 2013 web database forms.
  2. Anonymous Access: With this feature enabled Access web databases can be viewed by an anonymous read-only user without requiring authentication. We recently had a customer looking to provide an up to date inventory of their video game and pinball machine inventory to their web site visitors. With Access Services 2013 and anonymous access enabled inside the SharePoint web application, web visitors could view the entire catalog of available games and pricing information without authenticating to SharePoint. This is a powerful feature for any organization that wants to make their product inventory visible to any web visitor, delivering the information quickly and seamlessly without complicating the end user experience.
  3. Full control of SQL Server security: Access 2012 allows for the automatic creation of 2 SQL Server user accounts, one with read-only privileges and another with read-write.  While that is useful, some customers would like to extend this model to multiple user accounts. By creating multiple SQL logins via SQL Server Management Studio (SSMS)  you can create a much more complex security model for applications that want to leverage the Access 2013 web database information stored in SQL Server. Password complexity and aging requirements can also be enforced on these accounts.
  4. Full control of the network firewall: Many Access 2013 applications require extended security to comply with corporate or regulatory requirements. The Health Insurance Portability and Accountability Act (HIPPA) security requirements are a good example of this necessity. In a self-hosted or 3rd party hosted solution you have enough firewall configuration flexibility to lock down your entire database by imposing restrictions on the network perimeter based on TCP/IP address ranges, machine names, and network protocols. A combination of these restrictions can be imposed to address any security mandate.
  5. Render http links in the web browser control of an Access 2013 web database: The browser control is a powerful feature in Access 2013 web forms that allows you to call external resources into your application. Office 365 requires https for all external links which limits the use of browser based resources that do not support https.  This restriction can be lifted in a self-hosted or 3rd party hosted configuration.
  6. Customized backup: You can create a backup rotation scheme in SQL 2012 for the Access Web Apps that mirrors the site collection backup routine in SharePoint. This allows for a synchronized full fidelity backup of the SharePoint site and the Web Apps with multiple restore points. We recently assisted a customer who required a complete snapshot of their SharePoint and Access Services environment to be available for rollback to 24/47/72/96 hour recovery points. In addition, the second and fourth snapshots needed to be available in a secondary data center in the event of a problem with the primary facility. All of this is easily accomplished in a hosted configuration where both the SharePoint and SQL Server environments are completely controlled by the hosting organization.
  7. Ability to change Access Services configuration parameters and SharePoint web application settings:  When running Access Services 2010 alongside Access Services 2013 you maintain complete control of the SharePoint service parameters for Access Services. These parameters can be tuned to enhance the interaction between Access 2010 and SharePoint lists and  eliminate the “List Threshold Exceeded” errors that can appear when using the default configuration settings and manipulating large tables. Full support for web based reporting in published Access 2010 Web Databases and permissive file handling for things like PDF can also be enabled when you have full control over the entire SharePoint Central Administration console.
Posted in Access 2010, Access 2013, Office 365 | Tagged , , , , , | Leave a comment