Monday, August 20, 2007

Access Services for SharePoint

InfoPath client...Forms Services
Excel client...Excel Services
Access client...uh?

As SharePoint implementations evolve beyond content management and collaboration, there is often a need for custom applications with normalized data models. SharePoint's AllUserData table just doesn't cut it some times.

The business data catalog certainly enhances existing applications, but I think there is a real demand to replace those systems or create new ones. I also think that the value proposition for doing this type of thing with the current SharePoint product line is weak because it requires a lot of custom development.

I think Microsoft should provide the marketplace with Access Services for SharePoint. Perhaps such a feature could provide a way to upsize Access applications to SharePoint, upgrading the Access forms to ASP.NET web part pages and databases to SQL Server.

1 comment:

Kevin Parkin said...

I strongly agree. Sharepoint is overly constraining in the way it implements and displays tables
- the datasheet view wants to evolve into the web version of access.

Oh, and while they're at it, they should fix the bug where editing an item with attached files causes it to forget all such files when the approval behavior is turned on.

Blog Archive