Received an email today about Microsoft Script Center, and the evolution of what used to be called the 'Community-Submitted scripts'. The new TechNet Script Center allows you to upload scripts directly under your profile (Windows Live/Passport), draft and publish scripts (not unlike this blog), get ratings, and host a discussion board for each script.
In the bad old days, believe it or not, the method to submit scripts was to email them with the script in the body of the email to a Microsoft address. While it seemed low-tech, they were actually extremely reliable and pretty quick turning submissions around.
Like it a lot as a way to share some generic code snippets/modules, things that don't justify setting up a whole project with source control such as CodePlex.
Be sure to keep an eye on my TechNet Script Center Contributions. I'm posting a few that have been useful historically.
Thursday, September 10, 2009
Wednesday, September 9, 2009
Word 2007/MOSS Metadata Integration
Word 2007/MOSS Metadata Integration
Looked up some sites on how to pull data into a Word template from a MOSS List. Scarily examples with a ton of code embedded either in the doc or through a seperate .net app. Finally found a modestly stable technique that involved linking to the SharePoint list through an Access db, and then using that Access db as a source of a Mail Merge in Word. Not bad - unidirectional and has a few moving parts.
Then, this technique: Word 2007/MOSS Metadata Integration, uses a document library with columns, similar to setting up a list, then the columns can be used in a Word 2007 document with bidirectional updating.
Challenge I've ran into so far is versioning of the template, not seeing an easy way yet to update the template used on existing documents if columns are ever modified, added or deleted.
Looked up some sites on how to pull data into a Word template from a MOSS List. Scarily examples with a ton of code embedded either in the doc or through a seperate .net app. Finally found a modestly stable technique that involved linking to the SharePoint list through an Access db, and then using that Access db as a source of a Mail Merge in Word. Not bad - unidirectional and has a few moving parts.
Then, this technique: Word 2007/MOSS Metadata Integration, uses a document library with columns, similar to setting up a list, then the columns can be used in a Word 2007 document with bidirectional updating.
Challenge I've ran into so far is versioning of the template, not seeing an easy way yet to update the template used on existing documents if columns are ever modified, added or deleted.
Subscribe to:
Posts (Atom)
Labels
SQL Server
(15)
Project Management
(5)
Dot Net Framework
(4)
SSIS
(4)
Maxims
(3)
Virtual PC
(3)
WMI
(3)
ASP.net
(2)
Data Warehouse
(2)
Database
(2)
Development
(2)
InfoPath
(2)
Oracle
(2)
PMI
(2)
PowerShell
(2)
SQL Server Integration Services
(2)
Software
(2)
Source Code Control
(2)
web design
(2)
Active Directory
(1)
Business Analysis
(1)
C#
(1)
CSS
(1)
Career
(1)
Click-Once
(1)
Flash
(1)
FoxPro
(1)
HTML
(1)
IT Support
(1)
JavaScript
(1)
LAMP
(1)
MCP
(1)
MCTS
(1)
MOSS
(1)
Microsoft Access
(1)
Microsoft Money
(1)
ODBC
(1)
Office 2007
(1)
OneNote
(1)
Open Source
(1)
PMP
(1)
Reporting
(1)
SQL Server 2008 R2; SQL Server
(1)
SQL Server Express
(1)
SQL Server Reporting Services
(1)
SSRS
(1)
SharePoint
(1)
SharePoint Server
(1)
SkyDrive
(1)
T-SQL
(1)
UML
(1)
VB.net
(1)
VBScript
(1)
Visual Studio
(1)
WMI; PowerShell
(1)
Web
(1)
Word 2000
(1)
Word 2003
(1)
mashup
(1)