SharePoint Datasheet View and Office 2010 64-bit

If you have installed the 64-bit new version of Microsoft Office, Office 2010, then you will most likely see the following message when trying to edit a SharePoint list using the Edit in datasheet function:

The list cannot be displayed in Datasheet view for one or more of the following reasons:

– A datasheet component compatible with Windows SharePoint Services is not installed.

– Your Web browser does not support ActiveX controls

– Support for AxtiveX controls is disabled

 

The issue revolves around the fact that 64-bit versions of Office 2010 do not ship with the 32-bit Activex control that would make the datasheet option work with Internet Explorer.
There are ways to make this work, and the usual suggestion is to find a copy of an Office 2007 product and either install it (such as SharePoint Designer 2007) or just choose to install the Windows SharePoint Services components of the product. This works, but I don’t really want to go to that much trouble.
Another solution, and the one that I employed, is to install the 2007 Office System Driver: Data Connectivity Components. After installing the Components, go back to the menu and the datasheet option will work great.

Access Denied Message When Trying to Edit Properties of a List or Library Item

I created a new Office SharePoint Server 2007 Web Application a few months back and moved our existing sites around to create a new structure in the new Web Application. I did this to move all the project sites under one ‘roof’ and get things more organized. At the time, we were a little behind the curve on patching SharePoint. We were on version 12.0.0.6327, which is SP1 plus the August 2008 Cumulative update.

When new sites were created though, users were unable to edit the properties of anything they added to the site, whether a document or list item. As the SharePoint farm administrator, I received the Access Denied message as well when trying to edit the properties. The Access Denied message was also received when attempts were made to edit the properties of items within newly created Lists or Libraries on existing sites. Items could be added and deleted, but not edited.

While doing some research (see Technet Forums and Odole blog), I ran across several sites saying this was a known issue that is fixed in the February 2009 Cumulative update (for MOSS and WSS 3.0). I was told by Microsoft support after contacting them (see below) that the root cause is ACL corruption when the sites are moved.

After installing Service Pack 2 (for MOSS and WSS 3.0), and the latest Cumulative update (February 2010), the issue was not resolved for existing sites; but I expected this behavior. I contacted Microsoft support to obtain an executable (not publically available) that would fix the existing sites. After running the executable, the existing sites were all fixed and when I created a new site, it did not have the issue.

A screenshot of the fix program in action:

ListFixer

Mobile View Doesn’t Work on SharePoint ( WSS 3.0) List

I recently ran into a situation where I couldn’t get the ‘Mobile View’ in WSS 3.0 to work on a list that I had created. I went into the view of the list and selected the Mobile checkboxes (‘Make this a mobile view ‘ and ‘Make this the default mobile view‘), but it still was not showing up on my SharePoint site’s mobile homepage. My first thought was “What makes this list different than the other lists that have mobile views that are working?”

The answer was easy: I had created the list by selecting Custom List in Datasheet View from the ‘Create’ page. There are no mobile view choices for datasheet views, so I had created a new ‘standard’ view for the list. Even though I could check the ‘ Make this a mobile view ‘ checkbox, it was not showing up on the mobile homepage.

I basically had to recreate the list using the Custom List option, instead of Custom List in Datasheet View option. This is likely a bug; I haven’t been able to come up with a reasonable explanation as to why it would act this way (and the fact that the Mobile options showed up reinforce my bug theory).