I have seen some great articles about the 2007 Microsoft Office System, but if you are an architect or solution developer, this is one you don't want to miss: Compliance Features in the 2007 Microsoft Office System. This paper talks about business opportunities and technical aspects of extending the 2007 Microsoft Office system features to facilitate compliance.
Joanna Bichsel wrote this paper. She is a subject matter expert and she is doing an excellent job to help customers understand how to build Office Business Applications. She runs demos in developer conferences and her blog is a must stop. She will be posting a lot of short walkthroughs for developers and architects.
I loved this paper piece of art, and the two things I liked the most are:
I know there are tons of papers, documentation, webcasts, and technical articles. But this is one you should definitely send to the printer and enjoy.
PingBack from http://blogs.msdn.com/erikaehrli/archive/2006/12/01/TopTenOfficeDeveloperResources.aspx
Office compliance features are focussed on permissioning, not the control over production of financial data required for Sarbanes-Oxley compliance.
If you want to be able to setup checks and controls - that you didn't accidentally change one of your functions to a hardcoded value etc, that a daily price has actually changed and you haven't accidentally still got yesterdays - you need a full control solution like ClusterSeven.
[I don't work for them!]
Thanks Eric for pointing this one out: With the recent launch of 2007 Office System, it's always