Office Zealot

As yet I have not tested this, but it sounds good.  especially useful for large lookups, which in standard InfoPath are pretty painfully slow due to the massive amount of code that is produced by InfoPath Forms Services.  This method would mean that you could write your own code which is much more efficient.  Although to be honest ...

There seem to be some people in the big world of blogging that have posted that the correct way to get Outlook messages to be correctly crawled and made searchable within Sharepoint is to edit the registry. They are now out of date, as Microsoft have released a Filter Pack that provides this functionality, albeit undocumented. The 3 blogs I have ...

Well the underlying issue of my previous post was the fact that, when creating a calculated custom field referring to the system field ''Modified'' as part of the calculation in a document library, the value would change to 01/01/1899 when a document was modified.  This was very annoying so I attempted to find workarounds, although to no ...

Just been trying to find a good way of deploying these to different MOSS instances... e.g. Development, Test, QA & Live and also for giving to others for pre-sales demos. Thanks to Chris O'Brien for the very helpful pointers and code on this, check out his blog series at :  MOSS Artifacts Series These are implemented using Web Solution ...

If you have any lookup columns defined which will not appear in the site columns, it may be because the ReadOnly attribute is set to TRUE, try changing it to FALSE and re-installing and re-activating the feature and it should then display in the site columns list. At least this is what happened for me after much frustrated beating of my ...