There was an interesting question in one of the other posts that I thought I'd answer here to reach the broader audience:Doug said: If I export Northwind 2007 to WSS 3.0, the tables,
Microsoft Office 2007 Standard, like Customer, that contain 'Contact' type information get exported to an WSS 'Contact' content type. Very cool! Now you can view them in Outlook as a contact list.However, if I craft a table from hand with the exact same name,
Office 2007 Activation Key, and the exact same fields, and export it, it is exported as a 'Custom' content type and I get no Outlook love.What magic is done in Northwind to make this happen? I really want to be able to do the same thing.Great Question Doug! The answer is that Access keeps around a jet property named WSSTemplateID which enables us to correlate which tables have a built-in SharePoint list template equivalent. Here's a list of IDs for the different types we support out of the box: Contacts: 105Events:106Tasks: 107Issues: 1100 Here's a line of code that will set the WSS ID for contacts onto a table,
Microsoft Office 2007 Ultimate, so that when you try to publish it, you'll get the Contacts template in SharePoint. Just replace Table1 with your table name, and you should be good! CurrentDb.TableDefs("Table1").Properties.Append CurrentDb.CreateProperty("WSSTemplateID",
microsoft Office 2010 keygen, dbInteger, "105", False)Thanks for the awesome question,
Office Standard 2007 Key! <div
Office 2007 Activation Key Set SharePoint List Tem
Linear Mode
