Access 2013 RT SharePoint Designer 2013 Office 2007

[jrw1227]

A company for whom I work has an Access 2003 Runtime application with a SQL Server 2008 R2 backend which we recently updated to Access 2013 Runtime and SQL Server 2012 Express backend. We install Access 2013 RT, SharePoint Designer 2013 (for spell check), and if a new machine the Access client application. The spell check does as desired and the coding is a recommended several places on this site and others.

We have tested the application and it works unless we install Office 2007. This is the environment we faced at a location where we deployed the update files. Office 2007 is present which is why, when spell check failed to work at this location, we tested by downloading and installing Office 2007 at which time previously working spell check on the app failed and upon uninstalling Office 2007 it returned to working as desired.

The app, when a spelling error made in a control and lost focus occurs, selects the content of the control, which quickly disappears. No error is thrown, the app continues to work. Just the spell check does not. Office 2007 was installed prior to our deployment of the necessary Access 2013 related files.

Has anyone experienced a failure of and Access app using Runtime 2013 Office 15) and SharePoint Designer 2013 where Office 2007 is installed?

 

[Orthodox Dave]

Access Runtime is intended for distribution to those who don't have full MS Access installed.

I have no experience of this personally, but others have certainly had a problem with Access Runtime 2013 when full Access 2007, 2013 or 2016 are present:
https://support.chabadms.com/KB/a652/installing-access-runtime-2013.aspx

This one looks quite useful:
https://community.spiceworks.com/topic/1396732-runtime-access-2013

In that it appears you can run Access Runtime from full Access (but presumably of the same or higher version). If so, it would be better to uninstall Runtime than uninstall Full Access.

It should also be noted that 64-bit Access is incompatible with 32-bit Access (there are forums on how to get round this).

 

[jrw1227]

Jon,
Thanks for your response and the links. Unfortunately, while the first is good confirmation that a problem exists, the second does not apply as the Office 2007 does not have Access 2007 installed. The reason we installed the Access 2013 Runtime is because our application has been developed to run where users do not have any Access installed. We always inform our users that they must uninstall Office Access if they are going to use our application. It is part of our wiki prerequisites page.

As for the spell check, I installed Office 2007 Enterprise with a valid license key on my test virtual server and spell check stopped working. I left our Access Runtime app open while I uninstalled Office 2007 and spell check continued to fail after uninstall. Then I close our applicatino and reopened it and got Access 2013 Runtime install (I expect repair mode) and Configuration dialogs the first time and spell check worked as desired. The next time I opened the our Access Runtime app I did not get the install and config dialogs. I feel confident that this confirms that Office 2007 full version does not play well with Access 2013 (runtime). Spell check did work in Word 2007 but I tried to open Access 2007 and then open/create a database from a local template and it crashed.

I now can say with certainty that Office 2007 is interfering with spell check in Access 2013 Runtime and SharePoint Designer 2013 (for the spell check capability) when we run our custom Access Runtime application.

 

[Orthodox Dave]

Sorry that wasn't much help. Compatibility issues have been the bugbear of developers from the word go.

I have no more suggestions, other than the nuclear option of going back to the earlier versions of Access and Sharepoint, or upgrading Office in that other location.